> may not be the right place to ask, but more than likely the place where
> an accurate response will be given. Up and running with two current
> distributions of linux. hdb --> slackware kernel 2.1.106
> hdc --> redhat5.1
> Trying to get lilo to enable boot to either. Can't do it from either side.
> On the slack side /sbin/lilo creates correct ptrs to slack kernels on
> hdb but cant locate rh51 /boot/vmlinuz,
> on the rh51 side, vice versa, can get to rh51 kernels but not slackware.
> What gives? Using boot=/dev/fd0. Am forces to use two floppies,
> should only be using one.
>
Definitely offtopic here but the answer is prolly short:
mount the slack/redhat partition in redhat/slack... and edit the
lilo.conf's to point to the correct directories...
my current lilo.conf for example:
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
delay=50
image=/boot/vmlinuz-2.1.106
label=debian
root=/dev/hdc1
vga=1
read-only
password=foo
image=/boot/vmlinuz-2.0.33
label=debian-2.0.33
root=/dev/hdc1
vga=1
read-only
password=foo
image=/mnt/mnt/boot/vmlinuz-2.0.30
label=RedHat
root=/dev/hda3
# initrd=/mnt/mnt/boot/initrd-2.0.30
vga=1
read-only
password=bar
image=/var/linux
label=debian_install
# root=/dev/hdc1
append="root=/dev/ram"
initrd=/var/root.bin
password=fin
#outdated, to be updated for lilo20 syntax
#other=/dev/hdc4
# label=qnx
# table=/dev/hdc
# loader=/boot/any_d.b
# password=fin
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu