On 25/08/2024 at 22:48, Holger Wansing wrote:
Pascal Hambourg <pas...@plouf.fr.eu.org> wrote (Sun, 25 Aug 2024 22:03:28
+0200):
On 25/08/2024 at 19:03, Holger Wansing wrote:
I have prepared a netinst image for testing now with both above mentioned MRs:
https://people.debian.org/~holgerw/d-i__new-limits_and_fix-envelope-calculation/
(960 MB, sorry)
Wow, what makes it so much bigger than the 12.6 netinst image (662MB) ?
That's a follow-up from the GR decision, to include firmware in the
installation images, I think.
12.* netinst images also include non-free firmware. Firmware size has
increased, but not so much (106MiB -> 193MiB).
For the test image, I took the daily netinst image from yesterday and just
replaced the partman-auto and partman-auto-lvm udebs.
In other words, the latest netinst images are that big!
AFAICS, the daily amd64 netinst images are only ~750MB. Maybe the
firmware packages in /firmware and /pool are not deduplicated in your
image ?
The recipes give /boot a rather high priority: 5% of available space
(same as / which is much bigger), so the gap between the maximum and
minimum size (256MB) is reached with only 5.1GB extra disk space above
the minimum disk space (6.1GB for atomic and home, 8.7GB for multi).
Maybe I should lower the priority...
Maybe something should be changed.
If you provide the minimum disk size required to reach /boot maximum
size, I can adjust the priority accordingly.
Otherwise, we can skip the whole calculation for /boot completely:
if /boot reaches its maximum on a 10G disk (which is near at the absolute
minimum disk size these days) we should better go with a fixed size
of 1G for /boot (and ESP).
Actually with / minimum size of 8GB, minimum disk size for the atomic
recipe would be raised to 10GB, so the threshold would be raised to ~15GB.
