thansk to Vince Littles, Anders Johanssons, Emilio and Mark Wilson: http://lists.suse.com/archive/suse-linux-e/2000-Sep/1588.html a) I edited my /etc/fstab and had included the line: /dev/hda10 /mnt/Slackware reiserfs noauto,user 1 2 ...to this I used the command: $mcedit /etc/fstab (as root) b) remember to create a mounting point to the partition where slackware is: $mkdir /mnt/Slackware c) to test the mouting point, I just used the command line "mount" $mount -v /mnt/Slackware d) to to this directory to copy the Slackware kernel to boot properly. It is in /mnt/Slackware/boot. So go to: $cd /mnt/Slackware/boot e)In /mnt/Slackware/boot (warning: it is not /boot dir from your SuSE partition - now we are working at the Slackware's mounted partition) copy and rename the kernel: $cp -v vmlinuz vmlinuz.slak f) you should move the recent-created file /mnt/Slackware/boot/vmlinuz.slak to /boot rm -v vmlinuz.slak /boot g) edit the /etc/lilo.conf (in SuSE partition) in order to add this line to SuSE LILO menu: image = /boot/vmlinuz.slak label = slackware root = /dev/hda10 vga = normal read-only h) reinstall lilo: $lilo -v a. PS-anothers threads in this list that can help you: multiple distro installation (2000-Sep) LILO configuration (2003-Feb) Vince Littler escreveu:

On Thursday 20 May 2004 1:05 pm, Adagilson Batista Bispo da Silva wrote:

...

Thanks for replying, Vince! I prefer SuSE LILO and, as I said, it have been edited to put "slackware" as another option in /etc/lilo.conf (SuSE).

Vince Littler escreveu:

...

On Wednesday 19 May 2004 7:28 pm, Adagilson Batista Bispo da Silva wrote:

...

sorry, I don't understand yet what is missing in my lilo.conf (SuSE in /dev/hda6) to make my option "slackware" bootable. Slackware is in /dev/hda10 and the option "linux" (for SuSE) is booting. I can boot slackware with the cd-rom and entering: $bare.i root=/dev/hda10 noinitrd ro If I can boot with CD-ROM, so there is nothing wrong with the slackware partition. So, how could I make it bootable too, via boot menu of SuSE? Thanks for any help a. To understand my situation take a look at: http://lists.suse.com/archive/suse-linux-e/2004-May/2581.html

[...] So assuming that you will work with the SUSE LILO, you must refer to everything as seen by SUSE, even the Slackware. For example your SUSE lilo.conf includes:

image = /boot/vmlinuz label = linux append = "hdc=ide-scsi" initrd = /boot/initrd root = /dev/hda6 vga = 788

image = /boot/vmlinuz label = slackware root = /dev/hda10 vga = normal read-only

image = /boot/vmlinuz.suse label = failsafe append = "ide=nodma apm=off acpi=off hdc=ide-scsi" initrd = /boot/initrd.suse optional root = /dev/hda6 vga = 788

which says these things:

1] Your SUSE partition is /hda6 and slackware is /hda10

2] Your main SUSE kernel is /boot/vmlinuz and initrd is /boot/initrd as seen by SUSE

3] Your failsafe SUSE kernel is /boot/vmlinuz.suse and initrd is /boot/ initrd.suse as seen by SUSE

4] Your Slackware kernel is your main SUSE kernel with no initrd

You may have reason to boot Slackware with a SUSE kernel, but if SUSE requires the initrd, so would Slackware. More likely, you want to run Slackware with its own kernel. If this is the case, you must mount the partition with the Slackware kernel in SUSE and give the path to the kernel as SUSE sees it in lilo.conf, before running LILO in SUSE.

Checking lilo.conf (SLACK) build by Slackware itself, I can't see none initrd. Booting with CD-ROM the kernel bare.i works fine to me. I just have to enter manually: bare.i root=/dev/hda10 noinitrd ro (IMHO, it seems that it doesn't use initrd. Isn't it?!)

OK, seems that Slackware doesn't need an initrd. In which case SuSE probably doesn't... But leave that question for another day. For the moment, we have SuSE working with an intrd and Slackware without.

...

Trying to boot via SuSE LILO menu (option slackware) this error is appearing: Boot: /dev/hda10, loader /boot/chain.b Fatal: First sector of /dev/hda10 doesn't have a valid boot signature or yet Kernel panic: VFS: unable to mount boot FS on 03:10a Some more ideas? [], a.

Obviously you have changed your lilo.conf from the one posted earlier, because that never had/boot/chain.b mentioned. Obviously you are now in a panic and trying random stuff, without either actually understanding what you are doing or following the advice already given

There are no new ideas, please just follow the advice in Anders Johansson's post:

...

Basically, there are two ways of doing it. You can either use lilo from slackware, and set suse's lilo to use it as a chainloader, or you can mount your slackware partition from suse, and put the slackware kernel in suse's lilo so you boot it directly.

In other words, if you do it the way you have it in your suse lilo right now, you need to have slackware's partition mounted when you run /sbin/lilo in suse. You probably also want to set the image to point to the slackware kernel in /mnt/slackware/boot/ (or wherever you mount it)

The other way would be to do something like "other=/dev/hda10". It should work but I'm not 100% sure of the syntax

which is the same as my advice:

...

you must mount the partition with the Slackware kernel in SUSE and give the path to the kernel as SUSE sees it in lilo.conf, before running LILO in SUSE.