On Sun, Nov 25, 2018 at 1:54 AM Samuel Sieb <samuel@xxxxxxxx> wrote: > > On 11/24/18 1:20 PM, stan wrote: > > The only time grub-mkconfig runs is if it is run manually. On kernel > > updates a program called grubby runs and just copies the boot lines > > from previous kernels. So, if you want the new kernel boot line, as > > Oleg suggested, you will have to run, in /boot/grub2 or /boot/efi/grub2 > > (I think) grub2-mkconfig -o grub.cfg. I'm not sure of the directory > > with grub.cfg using EFI so check before you run that grub.cfg is in the > > directory. > > You don't need to run mkconfig at all. Just edit the last entry in the > grub config file and grubby will carry that over to each new kernel that > is installed. FWIW, I always re-run mkconfig after every kernel update nowadays, even if only to view the diff with whatever grubby did. I no longer trust grubby after several stuck instances in Amazon EC2, which I had to perform surgery on to repair because of https://bugzilla.redhat.com/show_bug.cgi?id=1509515 Grubby also has an annoying behavior of having menu ids which don't match the kernel name. While not a problem, it's different than what mkconfig does, and personally, I'd prefer we just run mkconfig after kernel updates. _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
