On 7/1/23 18:43, Tim via users wrote:
On Sat, 2023-01-07 at 14:36 +1100, Stephen Morris wrote:
I've just done an update which installed kernel 6.0.16 and I forgot
to run grub2-mkconfig, and when I booted from the grub menu's defined in
/boot/grub2/grub.cfg presumably updated by grubby, it did not run
initrd, the grub.cfg file generated by grub2-mkconfig does run initrd.
I have to ask, since I see a lot of grubby posts (pun intended):
I've *NEVER* run grub2-mkconfig. I've always just yum/dnf update (do
all current updates), or just dnf update kernel (if I wanted to
specifically just do that), and it's always installed the new kernel
properly all by itself. No further action was required by me.
What are people doing to their systems that they paint themselves into
a corner that they have to manually manage this, then have to pick up
the pieces when it doesn't work?
I have always run grub2-mkconfig both for legacy and uefi environments
because in the past grubby did not honour the configuration I specified
in /etc/default/grub. For example, I always specify that I want
sub-menus for all linux environments and grubby always refused to do
that, whereas grub2-mkconfig always did, hence I always used that.
regards,
Steve
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
