Hi again,
I'm trying to multi boot WinXP, fedora, and slackware. I installed Winxp, fedora, then slack in that order. It boots to Lilo from slackware and I can select slack or xp. What I tried to do was edit the lilo.conf to boot fedora as well. Fedora is on /dev/hda5. I can add it but when it starts I get a kernel panic. In fedora there doesn't seem to be a /boot/vmlinuz shortcut, but when I point it to that and run lilo I don't get errors. When I point it to the real kernel, i get errors.

This is my lilo.conf:

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/hda
#compact # faster, but won't work on all systems.
prompt
timeout = 300
# VESA framebuffer console @ 1024x768x256
vga = 773
# Normal VGA console
# vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# ramdisk = 0 # paranoia setting
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/hda7
label = Slackware
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/hda5
label = Fedora
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends
# Windows bootable partition config begins
other = /dev/hda1
label = Windows
table = /dev/hda
# Windows bootable partition config ends

Try moving fedoras vmlinuz file to /boot of Slack and in lilo.conf under the section for fedora, point to this vmlinuz, instead of just /boot/vmlinuz

Thanks,
I do that, leaving /dev/hda5 as the root, and it gets a little further but stops at SELinux initializing. GRUB was the bootloader for fedora, could that have something to do with it?

I believe that fedora uses intrd.img
initrd stands for initial ram disk. You need to copy this initrd to slakwares /boot. If you look under /boot of fedora you will see a file similar to initrd-2.6.x-.img Copy this to /boot of slaskware and under the fedora section add this line

initrd=/boot/initrd-2.6.x-.img

Worked like a charm! thanks so much

One is glad to be of service

Enjoy!

I was about to ask the same question (the same issue I had yesterday with my laptop when I installed FC4 beside my Slackware) when I stumbled upon this thread ('was actually searching the forum for an answer) and man oh man!, my problem has been solved following linuxlala's advise.

Thank you so very much!

oh and by the way, deftones, thanks for starting the thread.