Suitability for small disk sizes?

Hello all,

I see a number of threads regarding large update sizes and slow updates. Notably, the following:

I am playing with a cheap Chromebook that I have converted to be a Chrultrabook which has a 32GB eMMC. It installs just fine but the disk quickly fills up, presumably due to the update sizes.

Is there any way to manually trim this down or is it just not a good idea to try Bluefin on this system until the above issues are resolved?

Drew

Yeah, I know there are efforts ongoing and I will monitor them. I am thinking at the moment, this Chromebook may not be a good choice.

I tried the rpm-ostree cleanup stuff but it doesn’t clean much. My /ostree directory takes 17G even with no rollback candidate. On a lark, I reinstalled from scratch and the /ostree/ directory is 15G and the disk has 13G free. The Fedora specs list a minimum of 15G free and 20G recommended so maybe that’s all it is.

Drew

A specialized image with a stripped down OS designed for this would be the way to go.

Though I think you wouldn’t want to start from FROM silverblue like we do, you’d probably want to compose from the bottom up to make it as small as possible.

Thanks @Malix what model Chrultrabook are you using?

I do want to play with other systems so maybe I leave this one for NixOS and/or Guix.

Drew

For what its worth I run Wayblue with swaywm on my old Samsung Chromebook with 16GB of storage and 2GB of RAM, and a Celeon processor. Not a lot of applications are installed and no pinned deployments. I still almost ran out of space after updating but uninstalled some stuff I didn’t use. At this time, lower storage devices do suffer unfortunately.