Quote:
Originally Posted by sea
Maybe you had changed the "default=" value in either:
* /etc/default/grub
* /etc/grub.d/00_header
|
No, I haven't edited those files.
There is no specific value for the kernel mentioned in either one. In /etc/default/grub, the only relevant thing I see is the line "GRUB_DEFAULT=saved".
In /etc/grub.d/00_header all the values for defaults are kept in variables like $GRUB_DEFAULT.
In the thread I mentioned, one post says that updates modify the grub.cfg file by running grubby instead using grub2-mkconfig. So the grub.cfg produced by an update may disagree with what you get by running grub2-mkconfig.
This isn't a serious problem for me. I can take the original grub.cfg, which I saved and edit it by hand to make the machine text boot using the current kernel as the default. I'm just curious if there is a neater way to accomplish this.