registry team mailing list archive

[seasoned_geek <roland@xxxxxxxxxxxxxxxxxxxx>]

This bug has EVERYTHING to do with how the BIOS orders devices and how Grub 
just outright ignores that ordering despite the fact every other PC based OS 
can get that information from the BIOS and respect it.  They can even honor 
the device order selected by the user from the boot menu.

When Grub chooses the wrong *&)(&)(*&^ing drive as the boot drive, it updates 
the wrong MBR.


We have had this discussion many many many times.  The DOS emulator people can 
get it right.  The wine people can get it right.  FreeDOS can get it right and 
so can most other OSs.  Grub chooses not to.

On Friday, October 15, 2010 07:24:21 pm you wrote:
> @Seasoned_geek
> 
> Please re-read the bug description, this has nothing to do with how the
> BIOS orders devices. Additionally, it is impossible to reliably
> determine the BIOS's order from within linux which, among other reasons,
> is why grub2 instead identifies filesystems by UUID.

-- 
Roland Hughes, President
Logikal Solutions

http://www.theminimumyouneedtoknow.com
http://www.infiniteexposure.net

No U.S. troops have ever lost their lives defending our ethanol
reserves.

-- 
upgrades of the grub-pc package can overwrite wrong MBR
https://bugs.launchpad.net/bugs/496435
You received this bug notification because you are a member of Registry
Administrators, which is the registrant for Debian.