LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   using lilo to boot Slackware and puppy linux (https://www.linuxquestions.org/questions/slackware-14/using-lilo-to-boot-slackware-and-puppy-linux-779332/)

wufo 01-01-2010 09:43 PM

using lilo to boot Slackware and puppy linux
 
I have a question that is really probably a lilo question, but here goes.
Can you use lilo to boot different linuxes on separate hard drives. Like this.

/dev/hda1 - Slackware 13 with lilo in MBR
/dev/hdb1 - Puppy linux

Here is my lilo image area:

# Slackware 13 on hda1
image = /boot/vmlinuz
root = /dev/hda1
label = Linux
read-only
# Puppy 4.2.1
image = /boot/vmlinuz
root = /dev/hdb1
label = Puppy
read-only

Boots Slackware ok, but when booting puppy it screws up and seems to be printing the boot messages for the Slackware kernel on hda1.

Now, how do I tell lilo to find the puppy kernel?

wufo

~sHyLoCk~ 01-01-2010 10:27 PM

Did you try:
Quote:

other=/dev/hdb1
label=Puppy
table=/dev/hdb

~sHyLoCk~ 01-01-2010 10:28 PM

Make sure you re-run lilo.

bgeddy 01-01-2010 11:22 PM

This lilo.conf is not right.
Quote:

# Puppy 4.2.1
image = /boot/vmlinuz
root = /dev/hdb1
label = Puppy
read-only
This will be pointing to the Slackware kernel which is under /boot when you run lilo. This is how I've always setup lilo to multi boot.
First I mount my other linux partition somewhere visible to Slackware when I run lilo. Lets say you mount your Puppy partition to a directory you created /media/Puppy - i.e. in Slackware ..
Code:

su -c "mkdir /media/Puppy"
su -c "mount /dev/hdb1 /media/Puppy"

Then change lilo.conf like so :
Code:

# Puppy 4.2.1
image = /media/Puppy/boot/vmlinuz
root = /dev/hdb1
label = Puppy
read-only

Rerun lilo from Slackware and this should work. There are probably other ways of doing this but this always works for me.

wufo 01-02-2010 05:22 PM

Yep , I figured out the

image = /boot/vmlinuz
should be
image = /mnt/hdb1/boot/vmlinuz # the puppy partition slackware mounted

Now it finds and loads the puppy linux kernel, but the the screen blanks and the "caps lock" and "scoll lock" leds on the keyboard start flashing and hangs there.

Checked that puppy partion's /etc/fstab has "/", i.e. root directory, assigned to /dev/sdb1.

So I am stumped again.

Would have left puppy as sda and booted with its grub, but grub complained about the Slackware's ext4 file system.

wufo


All times are GMT -5. The time now is 10:31 PM.