On 11.10.2016 23:49, Ben Hutchings wrote: > On Tue, 2016-10-11 at 22:03 +0200, Helge Deller wrote: >> Package: partman-auto >> Version: 136 >> Tags: patch >> >> Can you please increase the default palo partition size >> (on the hppa architecture) to 45-50 MB. >> >> The reason is, that on a 64bit kernel we now have ~17 MB kernel size >> and ~20 MB initrd size (both can be stored in the palo partition). >> This sums up to 37 MB which already greater than the 35 MB we had up to >> now. Additionally we should keep room for the future, so 45-50 MB should >> be fine for the next few years. > > Then what happens when you upgrade to a newer kernel ABI version? > Shouldn't the limit be enough for at least 2 kernel and initramfs > images?
No. On hppa we have the palo partition and the /boot partition. In general the palo bootloader behaves like grub or lilo and boots any kernel out of a /boot partition. There you have space for multiple kernels and initrd images. In addition it's capable to keep one additional kernel & initrd (as fall-back) inside it's own palo partition (where the bootloader code itself is stored). This at least needed if you boot from CD/DVD or via tftboot where palo doesn't have a /boot partition, and it's possible to use the same technique on discs as well. Furthermore the "palo" userspace-tool to install palo and one (optional) kernel & initrd into the palo partition is not prepared to install multiple kernels/initrds either. And, usually people don't update this fall-back kernel/initrd either. So, it's safe to keep enough space for at least one kernel and initrd (plus some space for the palo bootloader code and room for bigger kernels/initrds in the future). Helge
