Bug#588303: grub-common: device.map order wrong since using uuids

[Colin Watson]

On Wed, Jul 07, 2010 at 09:32:17AM +0200, Mario 'BitKoenig' Holbe wrote:
> my device.map's device order changed since grub uses uuid device-names.

If device.map order is relevant *at all*, then you are doing something
terribly wrong.  device.map is going to go away once we remove the last
stealthy dependencies on it; you need to use more reliable ways to
identify devices instead.

> Before uuid device-names it was:
> 	(hd0)   /dev/sda
> 	(hd1)   /dev/sdb
> 	(hd2)   /dev/sdc
> 	(hd3)   /dev/sdd
> 	(hd4)   /dev/sde
> 	(hd5)   /dev/sdf
> This was actually even correct.

... unless Linux decided to reorder those devices on you, which may not
have happened to you personally but is common behaviour in general.
There's no point trying to hold on to the idea in GRUB that /dev/sda
should correspond to an earlier BIOS drive number than /dev/sdb, because
Linux doesn't guarantee that property for device names.

Did this actually break something for you?

> Just for the records: my EDD device order is:
> 	$ ls -l /dev/disk/by-id/edd-* | sed -e 's%^.*/dev%/dev%'
> 	/dev/disk/by-id/edd-int13_dev80 -> ../../sda
> 	/dev/disk/by-id/edd-int13_dev81 -> ../../sdb
> The other devices have no Volume ID (in fact, they have a zeroed MBR)
> and thus cannot be assigned to EDD devices.

We could sort EDD IDs first, although I don't know that it would gain
very much in practice.

Thanks,

-- 
Colin Watson                                       [cjwatson at debian.org]