I'm not building any kernels here. I am sharing the boot partition with various sorts of LUKS encrypted root partitions.
I understand now why it is totally fine to run your system with all kinds of kernels & initrds. It just works. I also have a patch for 30_os-prober that fixes things. (It has more problems, sometimes it has the wrong root-partition, and os-prober has various ways of collecting information about the systems to include for booting with grub (including parsing grub.cfg itself, which doesn't work so well when all these different root systems actually share the same grub.cfg). The way that works well for me is also enumerating the kernels based on the presence of the matching version in /lib/modules. But again, you could boot any root partition from any kernel, as I learned. In am not sure anymore why I wouldn't want to..?! It is sometimes handy to have the modules there, especially if you use dkms build systems or do other building. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1613260 Title: update-grub (grub-mkconfig) includes all kernels in boot, regardless whether version is in /lib/modules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1613260/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
