https://bugzilla.novell.com/show_bug.cgi?id=762095 https://bugzilla.novell.com/show_bug.cgi?id=762095#c1 --- Comment #1 from Michael Chang <mchang@suse.com> 2012-05-15 03:56:49 UTC --- Hi Andreas, Did you configure bootloader via yast2? If /etc/default/grub_installdevice missing, generally means configured info was missing (like the installed device (/dev/sda ..etc), activate partition or copy generic mbr or not ..). If perl-bootloader proceeds then it would use default value and somehow the outcome not very predictable. (should be not do install, no touch existing mbr and activate partition, so result would be only config renewed) However I could see in Grub1 these info are stored in menu.lst (use hidden magic, prefix them by ###), maybe we should consider to use the same way (in /etc/default/grub). This would eliminate the "Failed to open /etc/default/grub_installdevice" error. But it would silently run default for the hidden magic not found. Could you explain reproduce steps more elaborate then I could reference / reproduce. 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.

https://bugzilla.novell.com/show_bug.cgi?id=762095 https://bugzilla.novell.com/show_bug.cgi?id=762095#c3 --- Comment #3 from Michael Chang <mchang@suse.com> 2012-05-15 08:39:31 UTC --- (In reply to comment #2)

I set grub2 up ages ago - before your perl-bootloader changes went in.

Can't you get those values at install time from grub? Just check whether grub_installdevice and if not if grub has the data and if so, copy it to grub_installdevice?

The implementation is possible, maybe in perl-bootloader's %post section, or any other better place ? However my preference is get rid of /etc/default/grub_installdevice by merging it to /etc/default/grub (as comment#1 stats) and would not touch install device / activate / generic_mbr if they were missing (Simply because user haven't configured these items for grub2 in a way that upper managing tools aware of, so better don't touch them). Sync from grub should be a way to go and should work on most cases.. but may also have side effects if users get their grub2 installed manually on other locations we never know .. (basically we would suggest set /etc/sysconfig/bootloader:LOADER_TYPE=none if you want manually install bootloader, but your case somehow different). :( 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.

https://bugzilla.novell.com/show_bug.cgi?id=762095 https://bugzilla.novell.com/show_bug.cgi?id=762095#c5 --- Comment #5 from Michael Chang <mchang@suse.com> 2012-05-17 04:56:10 UTC --- I'd like to keep this open until I could know merging /etc/default/grub_installdevice to /etc/default/grub is better or not .. Procs : will not have annoying error of missing file anymore, however the trigger of the error might not be usual usage case. Cons : grub2 config holds untold magic that's used to store additional information (not used by any grub2's tool), which make grub2 config not unique to grub2. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=762095 https://bugzilla.novell.com/show_bug.cgi?id=762095#c7 Michael Chang <mchang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #7 from Michael Chang <mchang@suse.com> 2012-07-05 06:56:20 UTC --- As this case is caused by installed grub2 not ever configured via managing tools, close it as in this case user should set it to "none" to bypass perl-bootloader not disturb user's config. Please reopen if you still have problem. 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.