The value for saved_entry set by anaconda is bad ... that is,
incorrect. The only reason that things generally works is that if grub2
does not find a match, it defaults to the first menuentry and this is
generally what folks want to happen.
So, before I go about creating a fix, I am asking how folks want this
fixed because there are two options ... well, really three because there
is always the option of doing nothing.
From grub2-set-default --help:
MENU_ENTRY is a number, a menu item title or a menu item identifier.
Option 1. Set "saved_entry=0". This is valid and, until changed will
always boot the first kernel entry. One positive thing is that grubby
won't have to change.
Option 2. Set "saved_entry=<first_field_on_menuentry>" is valid. But
you will keep booting this after new kernels are installed unless you
change grubby. Depending on you point of view, this can be good or
bad. This is the purist's answer.
This old engineer prefers option 1 because grubby does not have to
change and things behave as most folks expect.
The user can always run grub2-set-default to set the wanted default.
Comments?
Gene
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
