https://bugzilla.novell.com/show_bug.cgi?id=781376 https://bugzilla.novell.com/show_bug.cgi?id=781376#c Lukas Ocilka changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|jsrain@suse.com |snwint@suse.com -- 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=781376 https://bugzilla.novell.com/show_bug.cgi?id=781376#c1 Michael Chang changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #1 from Michael Chang 2012-09-21 10:35:22 UTC --- Hi Dominik, How did you re-install grub2 in yast2 .. Did you switch to other bootloader(eg none) and back? 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=781376 https://bugzilla.novell.com/show_bug.cgi?id=781376#c3 --- Comment #3 from Michael Chang 2012-09-24 03:37:05 UTC --- Hi Dominik, Per your description, I think the behavior is correct. We don't write MBR each time you change settings via YaST, but only when a new install is proposed (eg, when you change to use that bootloader). This is to prevent MBR be written by our loader after it has been installed. People may install other loader and do anything we can't anticipate to the MBR so better don't touch it until user asks for a new installation .. Thanks, Michael -- 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=781376 https://bugzilla.novell.com/show_bug.cgi?id=781376#c5 Torsten Duwe changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED CC| |duwe@suse.com Resolution| |INVALID --- Comment #5 from Torsten Duwe 2012-10-11 13:49:40 UTC --- The _installation_ writes the generic MBR code. This should be obvious. If you destroy it afterward, the system won't boot until you rescue it or reinstall. The MBR code must work for multiple OS installations. The boot loader installation happens at system install time or when its code gets updated. This is loosely correlated but not identical. -- 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.