fr33z0n3r
December 3rd, 2016, 10:56 PM
I know that there is some awareness of issues related to old kernels hanging around in /boot. I'm curious if my config has an explanation for this. Ubuntu 16.04
Linux hostname 4.4.0-51-generic #72-Ubuntu SMP Thu Nov 24 18:29:54 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
I discovered today that /boot was over half full with about 10 kernels. So I ran
sudo apt autoremove --purge
Since then now I only have the following remaining. But I wonder about that oldest version. Why is it hanging around? Is this old kernel causing the lack of autoremoval?
/boot/vmlinuz-4.4.0-51-generic
/boot/initrd.img-4.4.0-51-generic
/boot/vmlinuz-4.4.0-47-generic
/boot/initrd.img-4.4.0-47-generic
/boot/vmlinuz-3.19.0-43-generic
/boot/initrd.img-3.19.0-43-generic
Linux hostname 4.4.0-51-generic #72-Ubuntu SMP Thu Nov 24 18:29:54 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
I discovered today that /boot was over half full with about 10 kernels. So I ran
sudo apt autoremove --purge
Since then now I only have the following remaining. But I wonder about that oldest version. Why is it hanging around? Is this old kernel causing the lack of autoremoval?
/boot/vmlinuz-4.4.0-51-generic
/boot/initrd.img-4.4.0-51-generic
/boot/vmlinuz-4.4.0-47-generic
/boot/initrd.img-4.4.0-47-generic
/boot/vmlinuz-3.19.0-43-generic
/boot/initrd.img-3.19.0-43-generic