Bug#1076952: [RFD] partman-auto: Update guided partitioning size limits for current and future needs
On 18/08/2024 à 16:00, Philip Hands wrote:
If the disk they're installing onto is huge, then having the upper limit
for /boot be 0.5GB larger will go unnoticed, whereas running out of
space on /boot is generally pretty annoying, or worse.
How huge ? I do not mind raising the maximal /boot size but it involves
doing a trade-off. With the current proposed 5% priority, which is quite
big, the partition reaches 1GB in 12GB disk space and would reach 1.5GB
in 22GB disk space. This is not huge at all. With 1% priority (the
minimal value with the current algorithm granularity), the partition
would reach 1.5GB in 80GB disk space (still not huge) but would now need
32GB disk space to reach 1GB instead of 12GB.
On 18/08/2024 at 16:38, Holger Wansing wrote:
Pascal Hambourg <pascal@plouf.fr.eu.org> wrote (Sun, 18 Aug 2024 12:33:50 +0200):
<https://salsa.debian.org/installer-team/partman-auto/-/merge_requests/15>
(...)
I would propose to change the template text for the new server recipe like
- Separate /var and /srv, swap < 1GB for servers
+ Separate /var and /srv, swap < 1GB (for servers)
Updated.
1.
I'm unable to produce swap partition bigger than 1G, even in a qemu VM with
2G or 4G of RAM
Sorry, I forgot to warn about partman-auto/cap-ram at first and added a
note to the MR description later.
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.
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 ?
Reply to: