UUIDs on drives

[Neil]

On 8/15/08, ghe <ghe at slsware.com> wrote:
>
> After the install, all was well; the number one SATA was sda. Then I
> turned on the SCSI disk and rebooted -- now the SCSI disk was labeled
> sda, instead of the SATA. Then Ubuntu updated the kernel, and part of
> that involves rewriting parts of /boot/grub/menu.lst; and when it did
> that, the system wouldn't boot anymore -- I think it wrote the boot
> block on the SCSI disk. I don't know for sure, but it wouldn't boot into
> Linux.
>
> OTOH, this is a very peculiar environment. There *is* no BIOS on the
> Mac, so I had to jump through a couple hoops to get Ubuntu to realize
> that and not try to use it.
>

<Just a semi-newb trying to clarify things for himself>
1. On a non-mac PC with a BIOS this would simply be solved by setting
the correct drive as primary, yes? Then Grub would see the "old" drive
as hd(0,n), yes?

2. Assuming the correct drive was recognised by the BIOS (or whatever
performs BIOS services on a MAC) as first and now as second the
correct thing to change in menu.lst would be hd(0,n) to hd(1,n), yes?

oh yeah: I love UUID's by the way, just try to run an emergency /home
from an USB disk for a week or two without em........

Neil


-- 
There are two kinds of people:
1. People who start their arrays with 1.
1. People who start their arrays with 0.