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.