Hi,
Pascal Hambourg <pas...@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 also attached the recipe files to this mail.
> I have not tested them at all yet.
Many thanks for this!
(I can better go testing and look at the resulting sizes in the installer,
instead of theoretically calculate the sizes around in beforehand... just my
2 cent, why I asked for a testing image.)
First, a little bit of nitpicking:
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)
More importantly:
the resulting sizes of the partitions look not that bad to me!
But some comments:
1.
I'm unable to produce swap partition bigger than 1G, even in a qemu VM with
2G or 4G of RAM
('cat /proc/meminfo' has "MemTotal = 2021952 kB" for example, when I start qemu
with '-m 2048M', so I assume everything is fine with the VM, right?
Or am I missing something?)
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).
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)
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...
I have uploaded some screenshots from tests with different disk sizes to
https://people.debian.org/~holgerw/partman-auto___new-limits/
Holger
--
Holger Wansing <hwans...@mailbox.org>
PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
