Bug#478254: modifying device.map seems to solve

[Robert Millan]

severity 478254 normal
retitle 478254 update-grub: guessing BIOS partition order is unreliable
thanks

The problem here is that you can't be certain about how the BIOS will
enumerate devices.  GRUB just guesses, which is sometimes not good.

A solution would be to switch to disk labels, uuid or something like that.

On Tue, Apr 29, 2008 at 12:11:02AM +0800, 杨朝晖 wrote:
> I just noticed /boot/grub/device.map, tried modifying it (exchange hd0 and hd1 mappings)
> and re-run update-grub. Now everything looks right and I expect later installation of 
> new kernels will boot successfully too.
> 
> Is this device.map the intended work-around for the problem? When and what program will
> regenerate it?

Yes, manual of device.map is the intended work-around.  It's only regenerated
when it's found to be missing, or when it's found to be incomplete/unusable.

-- 
Robert Millan

"The technological evasion of the license is as unacceptable as the
 legal evasion of the license [...].  That's the provision in section
 1 regarding keys. [...]  We say one thing: when you sell somebody a
 home... give him the keys"  -- Eben Moglen on GPLv3