LinuxQuestions.org - Lilo dual boot

- Linux - General (https://www.linuxquestions.org/questions/linux-general-1/)

- - Lilo dual boot (https://www.linuxquestions.org/questions/linux-general-1/lilo-dual-boot-212234/)

Hi,
Last night I've installed a new distro besides Slackware 9.1 and Windows XP.
I've edited the lilo.conf so it'll look like this :

Quote:

lba32
boot = /dev/hda
prompt
timeout = 300
vga = 773
image = /boot/vmlinuz
root = /dev/hdb1
label = Distro1
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
image = /boot/vmlinuz
root = /dev/hda6
label = Distro2
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends
# Windows bootable partition config begins
other = /dev/hda3
label = Windows-XP
table = /dev/hda
# Windows bootable partition config ends

Problem is that when booting onto Slackware 9.1, it uses the kernel of the other distro (because two images have the same name vmlinuz).

Why doesn't Distro1 use the kernel under /boot/vmlinuz on hdb1 and Distro2 the kernel under /boot/vmlinuz but on hda6?
Shouldn't the root entry specify what I want ?

Thank you.

Lilo reads /boot/vmlinuz when you run /sbin/lilo because it needs to load this into RAM before passing it any command line options. What you need to do is to mount the root partition of your other install (/dev/hda6 I presume) somewhere and edit lilo.conf so that image=/other_distro_mnt_point/boot/vmlinuz for the other distro. The root= option just tells the kernel which partition it should mount first. This must then contain the prerequisites for completing the boot (/etc/fstab, /bin/* and whatever else is required). It can't affect which kernel image is loaded.

thanks, that helped..

also u can copy ur vmlinuz,System.map,modules dir. of the other linux to /boot of current linux and then change the names and edit lilo.conf
this will also work