> >`LILO: slack' starts the Slackware OS but loads the Debian kernel image. >Note that whereas /vmlinuz in Debian is a symlink to /boot/vmlinuz-2.x.x, in >Slackware /vmlinuz is the kernel image itself.
I've never been able to divine the solution to this either, when using a 2nd or 3rd disk, so I use a workaround that has never failed me... And that is, put the kernels of ALL those Linux's NOT on the 1st disk into the /boot directory that lives there, on whatever partition that happens to be. With Lilo on the MBR, which is what I use here, this has done the job for me! I presently have one Intel box here that has 95, NT 4.0 and two bootable Linux OS's on it, and they all boot fine with Lilo. There is no partition of the 2nd Linux that lives on the 1st disk, and only the root of the 1st one does, for that matter. Paul
