Am 18. August 2024 21:50:53 MESZ schrieb Pascal Hambourg
<pas...@plouf.fr.eu.org>:
>
>> 2.
>> I wonder, if we could grow up the root partition in "separate /home" and
>> "separate /home, /var, /tmp" a bit (only relevant on small disks, most
>> probably).
>
>By raising the minimal / partition size or its priority ?
>The former also raises the minimal disk space requirement, whereas the latter
>is detrimental to other partitions growth. As above, it is a trade-off.
>
>> On a 20G disk, I get 4,7G for root, on a 50G disk that's 6,4G.
>> In current release, an installed GNOME or KDE desktop would consume the whole
>> root then, disk full (according to
>> https://d-i.debian.org/manual/en.amd64/apds02.html)
>
>Does this include the space required for two extra kernels ?
>apt autoremove keeps two kernels and removes the older only after the newer is
>installed, so there can transiently be three kernel installed.
Those values are directly after installation I guess.
So without several kernel images.
That's why we should just have spare space on /.
>> Of course, we cannot know, how users use their systems (DE installed: yes/no)
>> and 20G or 50G disk is probably small these days for default recipes, to get
>> good results for all cases?
>> And we might say, the "separate /home" recipe puts focus on the /home
>> partition
>> and therefore shrinks root. I'm not sure, what's best here...
>
>This is why I previously asked if there were intended use cases for built-in
>recipes which could be used as guidelines.
>For example, "allow to install and use a desktop environment within [TBD] GB
>disk space", and/or "allow to install and use a minimal (non-graphical) system
>within [TBD] GB disk space".
>Should the "small_disk" recipes be resurrected ?
I wasn't aware of such recipes, but what could be the benefit?
On such small disks you will best choose the atomic recipe, or
partition manually.
Holger
--
Sent from /e/ OS on Fairphone3
