Re: Boot better have mounted on root or /boot ?
On Sun 11 Apr 2021 at 14:33:22 (-0400), Felix Miata wrote:
> > On Thu 08 Apr 2021 at 14:37:59 (+0200), Marco Ippolito wrote:
>
> >> What would you consider in your future planning regarding sizing /boot?
>
> root@asa88:/boot# du -sh .
> 769M .
> root@asa88:/boot# dpkg -l | grep linux-image-4 | wc -l
> 10
Perhaps it should be pointed out that it's atypical to maintain such
a large number of individual systems on one machine. ISTR your having
more than a score of root filesystem partitions on one of your disks …
> root@asa88:/boot# dpkg -l | grep linux-image-4
> ii linux-image-4.19.0-1-amd64 4.19.12-1 amd64 Linux 4.19 for 64-bit PCs (signed)
> ii linux-image-4.19.0-10-amd64 4.19.132-1 amd64 Linux 4.19 for 64-bit PCs (signed)
> ii linux-image-4.19.0-12-amd64 4.19.152-1 amd64 Linux 4.19 for 64-bit PCs (signed)
> ii linux-image-4.19.0-14-amd64 4.19.171-2 amd64 Linux 4.19 for 64-bit PCs (signed)
> ii linux-image-4.19.0-2-amd64 4.19.16-1 amd64 Linux 4.19 for 64-bit PCs (signed)
> ii linux-image-4.19.0-4-amd64 4.19.28-2 amd64 Linux 4.19 for 64-bit PCs (signed)
> ii linux-image-4.19.0-5-amd64 4.19.37-5+deb10u2 amd64 Linux 4.19 for 64-bit PCs (signed)
> ii linux-image-4.19.0-6-amd64 4.19.67-2+deb10u2 amd64 Linux 4.19 for 64-bit PCs (signed)
> ii linux-image-4.19.0-8-amd64 4.19.98-1+deb10u1 amd64 Linux 4.19 for 64-bit PCs (signed)
> ii linux-image-4.19.0-9-amd64 4.19.118-2+deb10u1 amd64 Linux 4.19 for 64-bit PCs (signed)
… and I suppose that the contents of one of these partitions might
explain why you might still boot, say, a 4.19.12 kernel.
> Keep in mind, on average, each kernel release is larger than the last.
True, both the kernel itself and the amount that gets put into the
initrd. But also bear in mind that:
. if these kernels are all for just one system (which they appear to be),
several of the older ones could be uninstalled, but the .debs kept for
later reinstallation if and when required,
. if the kernels were for many different systems on the one machine,
the System.map/config/initrd.img/vmlinuz ensemble for several of
them could simply be moved to the day-to-day system's archive,
and copied back into place as and when required, to boot a
different, less frequently used system.
I think it's rare indeed to have to choose between ten different
kernels at the drop of a hat when booting up one system. What would
the use case be?
Cheers,
David.
Reply to: