On Thursday, 6 October 2022 15:41:52 CEST Ben Hutchings wrote: > > my laptop runs with a default partition layout created by Debian > > Installer 4 years or so ago: > > > > Device Start End Sectors Size Type > > /dev/nvme0n1p1 2048 1050623 1048576 512M EFI System > > /dev/nvme0n1p2 1050624 1550335 499712 244M Linux filesystem > > /dev/nvme0n1p3 1550336 1000214527 998664192 476.2G Linux filesystem > > > > The boot partition is now big enough to contain 2 kernel version, too > > small to contain 3, and too small to purge one and install another > > (somehow a bit more space is needed during install than is used at the > > end) > > The kernel team has had some discussion about changing linux-image > packages to not install vmlinuz directly in /boot ... > > This would potentially allow for smarter management of the available > space in /boot. That sounds like fixing the wrong problem or in the wrong place to me. The EFI partition gets 512MB, while boot gets 244MB? ... On a ~500GB drive? With the RPi images we had a discussion to increase the partition size* from 300MB to 512MB to accommodate several kernels. And that's on a minimal image which is (normally) written to a SD card. And my hesitation came from that people may be using 4 or 8 GB SD cards. Personally I never use the standard partitioning layout as it didn't make sense to me ... and IIRC that was from ~10 years ago. I don't know, but I expect there is some algorithm which determines what sizes the various partitions should get. Maybe that needs a new look to determine whether it is still the most sensible today? EDIT: I just looked up the thread on debian-devel and saw that d-i already has better defaults. That doesn't change my perspective that the fundamental aspect of /boot being too small should be addressed (directly) and not try to workaround it. *) Technically it's a partition mounted on /boot/firmware, but the kernels get copied into that partition.
Attachment:
signature.asc
Description: This is a digitally signed message part.