http://bugzilla.suse.com/show_bug.cgi?id=1093468
http://bugzilla.suse.com/show_bug.cgi?id=1093468#c4
--- Comment #4 from Jiri Srain ---
Well, it is not that simple with the MSDOS partition. The main question is: How
do you want to boot?
If the scenario is to chainload the bootloader from another one, then it can be
expected to install it into the logical volume and it can even work (depending
on what/how chainloads your bootloader).
However, if the goal is to load it by the generic MBR boot code, then
installing it into /dev/sda5 renders an unbootable system (you cannot set the
active flag on a logical volume, only on the extended partition holding the
volumes). That's the motivation behind using the extended partition (which has
always number 1 to 4).
That said: Even if current behavior is admittedly controversial, considering
not other reports, either it is a corner case which noone runs into, or current
behavior matches what (at least some) users expect - having the system in a way
that it can be loaded by the generic MBR code only via setting the Active flag.
--
You are receiving this mail because:
You are on the CC list for the bug.