https://bugzilla.novell.com/show_bug.cgi?id=773143 https://bugzilla.novell.com/show_bug.cgi?id=773143#c36 --- Comment #36 from Andrey Borzenkov <arvidjaar@gmail.com> 2013-02-21 11:04:08 UTC --- (In reply to comment #35)
If you haven't touched SetSettings() I think it's the reason why changes not be saved eventually.
No I did not. I only made it return "0" if saved_entry is missing in grubenv.
- after that grub2-mkconfig is run which now changes boot entries order so "Some entry title" is no more the first one
This seems to me a generic problem if we set an explicit entry. If we set it to, say "Advanced options for .... > openSUSE 12.2 with Linux 3.4.6-2.10-desktop" And received an kernel updates to different version ... would grub2-mkconfig handle that by updating the saved_entry as well as the config ?
Yes if it is using titles or (better) menuentry ids. No if it using numbers. As far as I see, it is using titles today (I did not check whether it builds correct entry for submenus though).
- now the effective default is no more "Some entry title" but whatever happens to become the first menu entry after grub2-mkconfig
But I suppose your patch will show the new default .. right ? If yes this is not a big problem to me. :)
Sure, yast2-bootloader will display the (new) first entry next time it is called.
Also if user changes GRUB_DEFAULT from "saved" to explicit menu entry this is going to be totally off mark.
I doubt any better people want to do that? It blows out things like grub2-reboot which used in hibernation (and other circumstance).
This is offtopic, but I still do not understand why grub-once depends on saved menu entry. I actually sent patch to upstream for discussion which is using separate grubenv variable for this. Zero response so far :) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.