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
On Wed, 2014-05-28 at 11:56 -0400, Gene Czarcinski wrote:
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.
I'm an old engineer as well then. I like option 1 better cause it does exactly the same as the current bad value and thus keeps the same behaviour.
anaconda-devel@lists.stg.fedoraproject.org