Jan Setje-Eilers writes:
> > What's the current word on performing a Live Upgrade from S10 FCS to
> > Solaris Express with newboot (and eventually back to S10 FCS)? I think one
> > issue was the lack of biosdev, which should be fixed by patch 117435-01.
>
> That should be all you need, I'm cc'ing Vikram who would know for
> sure.
In fact, I've completed the procedure I planned yesterday (i.e. add the S10
recommended patches which includes 117435, just to be safe), added snv_23
LU packages, and upgraded without problems. I had only one issue (which
should probably at least be documented): when running
luactivate <S10 FCS BE>
from snv_16 (i.e. newboot back to pre-newboot), that BE wasn't included in
menu.lst. This should either be fixed or at least the necessary procedure
documented.
> I might as well just confess what biosdev is used for. It allows BIOS
> device numbers (0x80 and the like) to be mapped to Solaris device
> names (/c0t0d0 and the like). The only thing that really depends on
> this is is the generation of the menu.lst root entry. GRUB uses BIOS
> devices names, but subtracts 0x80 from them, so that mapping is
> obvious. All that said, in most cases the GRUB root device will be 0.
> This is because the BIOS refers to _the_ disk it booted from as 0x80.
> So if you booted from the first IDE disk, that disk becomes 0x80, and
> if you boot from the second one, that disk will be 0x80. The only time
> this gets more interesting is if you have several disks (as you may
> with live-upgrade). In that case you may have GRUB on one disk, and be
> loading the OS from another. As long as you can somehow establish that
> mapping by hand you don't need biosdev.
>
> The way to establish that mapping by hand is to drop into the GRUB
> interactive shell and type "root(" then hit tab for the tab-completion
> to show you available devices. As you fill in more of the picture it
> will even tell you what filesystems it found on what partitions and
> slices.
Thanks for the thorough explanation: in fact, when I first tried LU from
S10 to snv_16, I just created a fake biosdev script that duplicated the
output of the real snv_16 biosdev. This was particularly easy since I did
the upgrade on a single-disk laptop :-)
Rainer
_______________________________________________
opensolaris-discuss mailing list
[email protected]