Problems with apt because root partition isn't big enough
-
I saw that many people have this problem.
Maybe stow (Link 1, Link 2) is something for you. You will also have to mount the root partition
rwand install stow, but this and the symlinks it creates won't take much space.Try following:
-
mkdir -p ~/Downloads/apt/cache && mkdir -p ~/Downloads/apt/archives && mkdir -p ~/Downloads/apt/lists && mkdir -p ~/Downloads/apt/installed -
sudo apt --download-only -o Dir::Cache="/home/phablet/Downloads/apt/cache" -o Dir::Cache::archives="/home/phablet/Downloads/apt/archives" -o Dir::State::lists="/home/phablet/Downloads/apt/lists" update -
sudo apt --download-only -o Dir::Cache="/home/phablet/Downloads/apt/cache" -o Dir::Cache::archives="/home/phablet/Downloads/apt/archives" -o Dir::State::lists="/home/phablet/Downloads/apt/lists" install stow -
cd ~/Downloads/apt/archives -
sudo mount -o remount,rw / -
sudo dpkg -i stow*.deb -
sudo apt --download-only -o Dir::Cache="/home/phablet/Downloads/apt/cache" -o Dir::Cache::archives="/home/phablet/Downloads/apt/archives" -o Dir::State::lists="/home/phablet/Downloads/apt/lists" clean -
sudo apt --download-only -o Dir::Cache="/home/phablet/Downloads/apt/cache" -o Dir::Cache::archives="/home/phablet/Downloads/apt/archives" -o Dir::State::lists="/home/phablet/Downloads/apt/lists" autoclean -
sudo apt --download-only -o Dir::Cache="/home/phablet/Downloads/apt/cache" -o Dir::Cache::archives="/home/phablet/Downloads/apt/archives" -o Dir::State::lists="/home/phablet/Downloads/apt/lists" install glmark2-data=2014.03+git20150611.fa71af2d-0ubuntu7 glmark2-es2-mir -
for f in `ls -1 *.deb`; do dpkg-deb -x $f /home/phablet/Downloads/apt/installed; done -
sudo stow --stow --dir=/home/phablet/Downloads/apt --target=/ installed -
glmark2-es2-mir
To undo:
-
sudo stow --delete --dir=/home/phablet/Downloads/apt --target=/ installed -
rm -rf /home/phablet/Downloads/apt/installed/* -
sudo dpkg -P stow -
sudo apt --download-only -o Dir::Cache="/home/phablet/Downloads/apt/cache" -o Dir::Cache::archives="/home/phablet/Downloads/apt/archives" -o Dir::State::lists="/home/phablet/Downloads/apt/lists" clean -
sudo apt --download-only -o Dir::Cache="/home/phablet/Downloads/apt/cache" -o Dir::Cache::archives="/home/phablet/Downloads/apt/archives" -o Dir::State::lists="/home/phablet/Downloads/apt/lists" autoclean -
sudo mount -o remount,ro /
Eventually:
rm -rf /home/phablet/Downloads/apt
You can also do things like:
apt-cache -o Dir::Cache="/home/phablet/Downloads/apt/cache" -o Dir::Cache::archives="/home/phablet/Downloads/apt/archives" -o Dir::State::lists="/home/phablet/Downloads/apt/lists" madison glmark2-data
-
-
Hello @bbiw
This is not a problem and this is not something we want users to do.
The reason is if they are not able to fix this themselve then they probably should not try this.We don't want people come back and complains about having bricked their device because they didn't understand why Ubuntu Touch is image based.
As we frequently say, a phone or a tablet are not regular computers.
For the purpose of Ubuntu Touch, we decided to go with ease of use and daily driving capabilities, so the image should be stable and users are restricted to prevent issues from the user.
There are enough quirks and trade-offs to live with as it is...But thanks for pitching in some ideas for people who understand the risks.
-
You're right. Btw. Fairphone 4 is not really image-based as the root partition is a device-mapper device (dm-0) defined as a part of the super partition. If it would be image based with an ubuntu image living at /userdata, like in the old days or other devices, i don't know, it would be easy to just extend this image. I wonder why someone chooses to install Ubuntu Touch with zero knowledge about Linux or Ubuntu but it's up to them and of course it's better for a developer to take care that they don't brake their system. As superuser you will always have to know what you're doing, SO FIRST THINK, THAN "Return".
The biggest problem i see with UT are the proprietary drivers. Even with libertine there's no e.g. hardware acceleration. By using stow and the symlinks it creates i can, at least with glmark2-es2-mir, have hardware rendering.
-
@bbiw said in Problems with apt because root partition isn't big enough:
The biggest problem i see with UT are the proprietary drivers. Even with libertine there's no e.g. hardware acceleration. By using stow and the symlinks it creates i can, at least with glmark2-es2-mir, have hardware rendering.
You seem to have enough knowledge to contribute to the port for the device(s) that you own.
I may be a technical person, but I don't know enough on this topic.To fix your issue with hardware acceleration, you might want to have a look at the porting documentation.
Try to build the image from source and see what you can do to improve the experience with the Fairphone 4 for everyone else.My mother uses Ubuntu on her laptop without any knowledge about Linux and I hope they soon might be willing to give Ubuntu Touch a try.
To me, the goal is to bring an alternative to anyone willing to regain control over their data.
Doesn't matter if they know how to tinker with their phone. And that's also what I want for me.I use Linux since 1995 and I never used Windows on a personal computer since 2001.
I know my way around things but what I like is that I don't need to if don't do something stupid.
And I expect the same for my phone. I have 3 devices with Ubuntu Touch, one is my daily driver and is often on Stable or on RC just to be sure that an OTA won't break my phone. The others are to tests things out and improve my knowledge of our OS and maybe one day I will be able to make a port. -
I expressed myself wrongly, sorry. Hardware is working fine, i think. Because of the root partition size limitation i already tried with libertine and self-made chroots or lxc containers and vnc.
That's where the problems begin, e.g. only software rendering through mesa. I've already tried a lot of things, e.g compiling libhybris against the vendor "blobs" or mesa drivers with Adreno support, but nothing works as expected.
It's okay for me, because i'm no expert. Understanding the whole system is far out of my reach, i think.
I read about the Ubuntu Touch architecture and thought about rebuilding this in a chroot, which includes mounting the android rootfs image and every other mounts, but i fear that won't be enough to have real hardware support.
I don't understand how this all works together with QML, Mir and so on. I've searched the internet a lot, but there isn't much information about that. Maybe it's a secret or something, I don't know.
Perhaps it's too hard, otherwise it would already be implemented in libertine or something.
-
@bbiw said in Problems with apt because root partition isn't big enough:
Maybe it's a secret or something, I don't know.
It is not a secret, as it is all Open Source.
But yes, documentation is severely lacking, as is the case with many other Open Source projects.
In our case this is due in part to the complexity of the subject matter. And also because those that know the most about this have the least time to document it. -
Unfortunately, because there are so many questions i still have and this lack of documentation makes it hard to learn and understand.
-
@bbiw One way to improve the documentation is writing down everything you learn and contributing that as documentation. In that way slowly the documentation situation will improve.
