http://bugzilla.novell.com/show_bug.cgi?id=496002 Zheng Chen changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zchen@novell.com AssignedTo|bnc-team-screening@forge.pr |nld10-bugs-qa@forge.provo.n |ovo.novell.com |ovell.com -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=496002 User rw@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=496002#c1 Raymund Will changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |coolo@novell.com, | |rw@novell.com Version|Alpha 0 |Milestone 8 Severity|Normal |Critical --- Comment #1 from Raymund Will 2009-10-05 09:28:35 MDT --- This seems to be broken still... :-( The real issue is IMHO, that settings on the "Boot Loader Installation" tab do in no way impact check-boxes concealed behind that "Boot Loader Options" button. This leads to nonsensical, contradictory settings: you can't possible eat the cake and keep it! In other words: you can easily write a generic loader *and* grub to the MBR, but you can only read the last thing written! The same is true for "Set active Flag for Boot Partition" without having one. And it's IMHO a blocker bug to activate an 'Extendend Partition", if nothing is to be installed there, only because the initial proposal of YaST had such a setup! -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=496002 User jsrain@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=496002#c3 Jiri Srain changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #3 from Jiri Srain 2009-10-08 02:23:51 MDT --- The described behavior is correct. You cannot set the Active flag to volume inside a logical partition or MBR. If bootloader is installed into MBR (as it was), YaST sets the flag to the partition where the /boot directory is located. However, it is inside the Extended partition, therefore the flag was set to the Extended partition. In general: If you install bootloader into MBR, there is no reason to change the boot flag if it is set to any existing partition. On the other hand, there are some (especially older) BIOSes which need the active flag to be set, otherwise they will not boot. Since BIOS correctness cannot be detected, YaST suggests to set the flag by default. It is strongly recommended to have a primary partition for bootloader (the /boot directory), we do not support scenario as you described (although in general it works). -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.