Re: Booting OSR504 from Ranish Boot Manager
From: Bela Lubkin (belal_at_sco.com)
Date: 04/26/03
- Next message: Bob Bailin: "Re: Adaptec RAID 2110S on SCO OS 5.0.7"
- Previous message: Bela Lubkin: "Re: TCP/IP seems to fall over."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: 26 Apr 2003 08:55:22 -0000
Carol Saah wrote:
> I do not have a Windows OS on the 1st drive and I would like
> to figure out a way to dual boot with boot partitions for SCO OSR504
> and Solaris 9 (12/02) on the 1st drive other than using a boot diskette for
> 1 of the OS's.
>
> After research and lots of testing, I believe that I cannot boot Solaris
> from SCO OSR504's bootos
> partition# and OSR504 from Solaris's boot manager because both OS's require
> active partitions
> for their OS partition bootstraps.
You're using a 4-month old version of Solaris, and an OpenServer that
was shipped 6 years ago...
OpenServer 5.0.7 no longer has this requirement. It can boot from a
non-active partition, as long as that is the only partition of the
System V Unit partition type. I don't know what partition type number
Solaris x86 uses. OSR5 and UW7 both use 0x63 (which is an ongoing
irritation -- even with OSR507, you cannot have both on separate
partitions and boot OSR5 from the non-active partition, because it'll
see the active UW7 partition as the one to use).
> Another thing that I have consistently noted is that SCO's partition
> pointers (#'s) to
> partitions 1 and 4 are switched to 4 and 1 in Solaris and Ranish PM. SCO's
> partition
> pointers to partitions 2 and 3 are switched to 3 and 2 in Solaris and Ranish
> PM. What is
> the deal here? It isn't even that easy, though. If there are 2 OSR504
> partitions on the system,
> SCO OSR504 puts those partitions as 1 and 4 and the others are 2 or 3. The
> bottom line
> is that the partition #'s that OSR504 uses are NOT the same pointer #'s that
> Ranish and
> Solaris use. Ranish and Solaris 9 partition "pointers" are consistent.
I looked into this long ago and only half-remember what I learned. I
think it was this: the OSR5 kernel code that reads the partition table
breaks it out into a data structure which it lays down in reverse order
to the on-disk partition table. So all utilities in OSR5 call what
other OSes call partition 1, partition 4; and so on.
That doesn't explain what you saw with two OSR5 partitions. Your
description isn't clear enough for me to guess what really happened.
>Bela<
- Next message: Bob Bailin: "Re: Adaptec RAID 2110S on SCO OS 5.0.7"
- Previous message: Bela Lubkin: "Re: TCP/IP seems to fall over."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
