Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Multibooting redhat linux 5.2 and SCO OSR5.0.4

0 views
Skip to first unread message

Salman Ashraf

unread,
May 2, 1999, 3:00:00 AM5/2/99
to
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. 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


Mike Kenyon

unread,
May 4, 1999, 3:00:00 AM5/4/99
to
> 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. 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

eculp...@hcc-care.com

unread,
May 5, 1999, 3:00:00 AM5/5/99
to
In article <372CC813...@bigfoot.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 ------

0 new messages