https://bugzilla.novell.com/show_bug.cgi?id=771587
https://bugzilla.novell.com/show_bug.cgi?id=771587#c11
--- Comment #11 from Michael Chang
(In reply to comment #8)
Yes. It's true. (A reboot is necessary for the upgraded kernel)
No, it is not for x86_64.
And the config parsing in grub2-once is not nice and is error-prone. I bet this will get back to us soon as boomerang. (Unless you push the script upstream where developers ensure it's up-to-date.)
I don't think upstream would review the grub2-once as it's distro specific (like the grubby or grubonce) ?
Why do you think so? grub2-once looks like a good feature to me.
It's not fundamental, as the grub-reboot is the building block, the grub2once usage is more restricted. It's created to be easier to interface with openSUSE pm-utils and, afaics, Fedora, Ubuntu takes different approach and means. That why I think it's distro specific (the same role as grubonce and grubby)
I'd suggest a way to disable the submenu, this would relief the people (or utilities) who want to use grub2-set-default or grub2-reboot. It's cumbersome to specify the full hierarchy of the boot entry, instead of a simple name or index.
I can see upstream has a bug for it: http://savannah.gnu.org/bugs/?36850
To tell the truth, I don't understand why submenus were introduced at all. I think they make things much worse.
It's panful when you want to set default entry you have to give a looooong entry name, the xen case is even much more worse as it has 3 levels .. it's very easy to make mistake in manual. Also the default highlight is confusing, it's not on the inner-most menuentry, but on the outer-most (1st level) of submenu. In contrast to other bootloader config, which is much more easy and numeric index is acceptable.
This would get rid of the complexity and grub2-once can be avoided. That is we could wrap grub2-reboot with a much more easy script ..
Whether the config parser would reliably work is important, with my limited ability this is what I could do so far. If it can't pass the review here then I agree we'd better not proceed with a fix this way.
Yes, it works now, but it will definitely break with next release. Grub2 developers are crazy, so that they will change the config structure.
I think the grub2once should cover the case of "no submenu" (aka only menuentry directive is used in the config) as it's a special case of submenu. Unless the meaning of submenu or menuentry has changed, the grub2once should be guarenteed to work (otherwise it's considered a bug) :) Thanks, -- 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.