Multibooting redhat linux 5.2 and SCO OSR5.0.4
Salman Ashraf
to use LILO as a boot loader. Linux is installed on /dev/hdb and lilo is
in the MBR. I installed SCO on /dev/hda, which already has win 98 on it.
After SCO was installed, I guess it put its boot loader in the MBR
because I'd get the SCO Boot: prompt when I'd boot my machine. So,
I booted linux from the floppy and reran lilo after adding a clause for
SCO in lilo.conf. It's something like
other=/dev/hda3
loader=/boot/chain.b
label=sco
But when I tried to boot into SCO, it wouldn't boot. It would just hang
saying booting sco. I have to use the SCO boot and root disk to get into
SCO, but then I suppose I need to mount my root filesystem from the hard
disk or something because what I get from the floppy isn't all of it. If
someone has a similar setup and can boot SCO successfully from lilo or
just knows how to do this, I'd really appreciate any help. I need to get
this running pretty soon. Thanks in advance.
Salman
John Gray
please see SCO TA 106287 103327 106107 You will need to read them
in full. To start you will need to change the device nodes for the disk
to point
to the absolute partitions according to the way they are seen from the SCO
fdisk. This will include /dev/root rroot swap rswap stand rstand and
anything
else you have created. The /dev/dsk/ /dev/rdsk/ /dev/hd /dev/rhd
entries too.
once you have done that you will need to change the /etc/conf/node.d/hd
file
and the /etc/conf/cf.d/sassign file because the sassign has floating
minors.
last but not least the /etc/default/boot will need a tweak to tell boot
where
to grab the /unix binary.
The minor number scheme by default has the disk driver keying off the
active
partition. In this way you can have multiple installs of SCO and they
will all work
together. The procedure (more of an outline) listed above changes
this to
use the absolute position of the OS. IT does work, I have done it
several times.
Keep in mind that there are three phases that you need to keep
functional.
1) /boot where does it look to get the kernel? hd(40)unix
-> hd(24) unix ????
2) /unix Where does the kernel think the root file system and
swap are?
3) utilities When you run the system commands where are they going
to be getting
the info they are requesting. Make sure the
device nodes point to the
part fo the disk that the kernel is looking.
Remember the kernel doesn't
care. If asked to get X bytes from the wrong
partition it will.
Hope this helps.
-john
Mike Kenyon
> to use LILO as a boot loader. Linux is installed on /dev/hdb and lilo is
> in the MBR. I installed SCO on /dev/hda, which already has win 98 on it.
To recap: Linux is on /dev/hdbn, Win 98 is on /dev/hdax, and SCO on /dev/hday,
where n, x and y are the respective partition numbers.
> I booted linux from the floppy and reran lilo after adding a clause for
> SCO in lilo.conf. It's something like
> other=/dev/hda3
> loader=/boot/chain.b
> label=sco
> But when I tried to boot into SCO, it wouldn't boot. It would just hang
> saying booting sco.
I'm not a lilo expert by any stretch of the imagination, but I'll have a
guess. Does lilo report any errors on being run? I suspect lilo may not be
able to see the boot division of the SCO partition and thus doesn't know where
the boot loader is. Can you not get the SCO bootloader to boot Linux? The
instructions on setting up the OS/2 boot manager or the NT OS loader may be of
help here, failing anything else of use, as lilo is these cases is only
installed on the partition boot sector, not the MBR.
Good luck!
--
Mike Kenyon <mke...@promtek.com> Software Engineer for Promtek Ltd
Robin Grayson
With both Windows 98 and SCO OpenServer 5.0.4 residing on your first hard disk,
is the SCO OpenServer boot partition within the first 1024 cylinders of the
hard disk?
Also, I seem to remember having problems if SCO OpenServer wasn't the active
partition, but it did at least get to the hwconfig screen.
eculp...@hcc-care.com
Salman Ashraf <tab...@bigfoot.com> wrote:
> I have Redhat 5.2 and SCO OpenServer 5.0.4 on a machine and I would
like
> to use LILO as a boot loader.
FWIW:
I have OpenServer 5.0.5 and Redhat 6.0 (just upgraded from 5.2)
dual-booting with lilo. Here is how I did it.. YMMV.
System has 3 disks. 1 SCO 2 Linux. SCO disk is active and is /dev/sda
Linux disks are /dev/sdb and /dev/sdc. Here is my lilo.conf
boot=/dev/sda
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
other=/dev/sda4
label=sco
table=/dev/sda
image=/boot/vmlinuz
label=linux
root=/dev/sdb1
initrd=/boot/initrd.img
read-only
The SCO partition is active. When lilo is ran from Linux it writes the
loader to the MBR. When rebooting the lilo prompt comes up and typing in
sco will load the SCO boot prompt. Kinda flakey but it works for me.
----- Posted via Deja.com, The People-Powered Information Exchange -----
------ http://www.deja.com/ Discussions * Ratings * Communities ------