sd, sd, who's got the sd - f7 work required before release!

[Styma, Robert E (Robert)]

> >>>> How will the two FC7 systems detect the new drive?
> >>>>
> >>>> Is there a method to the madness?
> >>>
> >>> This is why we use disk labels or UUIDs instead of device 
> names. With 
> >>> changes like this in the kernel and especially with machines with 
> >>> removable drives, or machines using fancy multipath storage, it's 
> >>> nearly impossible to reliably predict exactly what order 
> the drives 
> >>> will be found in.
> >>>
> >>> So the solution is: just give the partitions names 
> instead. Then it 
> >>> doesn't matter if your FC6 root drive is sda1 or sdb1 or 
> hdc1, it's 
> >>> always LABEL=fc6_root. If you say "mount LABEL=fc6_root 
> /fc6" it will 
> >>> Do The Right Thing.
> >>>
> >>> So, in short, it doesn't matter how the two FC7 systems 
> will detect 
> >>> the new drive, so long as you give it a useful label.
> >> Will, you could have mentioned:
> >> 1. a command to set the label ?
> >> 2. whether an lvm label like LogVol01 or LogVolhome is the 
> same as the 
> >> label you are mentioning ?
> >>

So it appears the answers are as follows:
1.  /dev/sd* assignments are not easily predetermined.

2.  You are safe if you label every partition and always use partitions.

The critical issue to me was to avoid the situation where you add a new
drive
to an existing system and because of /dev/sd* assignments end up with a
non
bootable system.

The issue of how the device maps work in the /boot/grub/device.map and
how
the sd* values are mapped into (hd0) etc. throws another wrinkle into
the
mess.

Bob S
Phoenix, AZ