https://bugzilla.novell.com/show_bug.cgi?id=765198
https://bugzilla.novell.com/show_bug.cgi?id=765198#c7
--- Comment #7 from Neil Rickert
In general you shouldn't check "Boot from /boot" when /boot is logical partition, as the generic mbr boot code couldn't bootstrap it directly.
Here are some general principles: 1: If you have more than one operating system installed, then only one of them can be booted directly. The others must be booted indirectly. 2: People who do beta testing are likely to have more than one operating system installed. 3: There is only one extended partition, so only one operating system can boot from the extended partition. 4: The active flag is only relevant to the one system (or boot manager) that is booted directly. Any installed system that is booted via another boot manager should not need an active flag (though some operating systems do seem to need that flag before they will boot). In my case, I have a booting arrangement that has worked and that I am happy with. So when I install a system for testing, I don't want it to mess up a booting arrangement that works well. In the case of my "computer 2" (a Dell laptop), I also have Windows 7 and opensuse 12.1 installed. I have an entry in the boot loader for opensuse 12.1 which chain loads to boot whatever is in "/dev/sda5". The best for me is to install Beta1 to boot from "/dev/sda5" and not set the active flag, so that I can boot it the way I am already set up for booting test systems. If I allow it to install grub some other way, then I have to change the active flag to what I want with "fdisk" and I have to use "dd" to write the boot sector to "/dev/sda5". I seem to recall that I had to go through those steps with the M3 release, because the grub install did not have enough options for what I need. -- 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.