On Fri, 14 Apr 2000, you wrote:
> Well, after all, I cannot boot off of anything on the second disk.
>
>snip
>
> Then I tried Lilo, and that doesn't work either. I have the following:
> hdb1 is my Mandrake 2 /boot partition
> hdb11 is my Mandrake 2 / partition
>
>snip
>
> Lilo won't accept anything I try for the second disk. I have tried:
>
> image=/boot/vmlinuz
> root=/dev/hdb1
> label=md
>
No, this is wrong (unless you have mistyped in the Email)
You need
image=/wherever hdb1 is mounted in the RUNNING version/vmlinuz
root=/dev/hdb11
label=mandrake
read-only
Note that hdb1 must be mounted in the version that you use to run lilo and
'image' points to the full path to the kernel, or to the link that points to the
kernel. 'root' points to the partition (not the mount point, it need not be
mounted) where the / directory for the installation is.
In reply to another comment which I think is the same thread, anyway it is
relevant:
I have three different distributions installed on this PC, each
with its own /boot and / partitions, sharing /usr/local = /opt, swap and /home
partitions. I had no serious problems in installing RedHat 5.0 and 6.0,
Caldera 2.?, SuSE 6.2 or Mandrake 6.0 and 7.0 (not all at once!) using this
setup. Corel failed because I couldn't find out how to make it use the existing
partitions. At the moment I have lilo on a floppy, but there is no
problem in having lilo on the boot sectors of hda, booting Linux on hdb. You
just need
boot=/dev/fd0
or
boot=/dev/hda
in the global section of lilo.conf
It is a nuisance creating the lilo.conf file for several distributions
because you have to mount all the /boot partitions so lilo can find the
kernels. I mount them in /etc/fstab as, for example, /mnt/redhatboot and
then they are always there and not in the way.
I don't recommend the shared /home partition. I tried to get over the problem of
different .*rc and similar files for different distributions by calling myself by a
different username with each distribution, but then you have files owned by a
user who doesn't exist for that distribution - not a disaster, but confusion.
Good luck, keep trying!
Edward
[EMAIL PROTECTED]