LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Touble dualbooting different Linux os' (https://www.linuxquestions.org/questions/slackware-14/touble-dualbooting-different-linux-os-119893/)

Kjetil4455 11-25-2003 05:01 PM

Touble dualbooting different Linux os'
 
Ok, here's the prob;

i use slackware regulary, right?

but i'd like to dualboot to debian, cause i wanna check it out.

my lilo.conf's set up correctly and stuff.

but when i try to load debian, it loads the kernel from my slackware partition. (which is doomed). how can i make it load from its own root?

kasperhans 11-25-2003 05:06 PM

then your lilo is not setup right you have to specify the location of your debian kernel in lilo for dual booting read the lilo conf on that should work though

Kjetil4455 11-25-2003 05:07 PM

yeah

image=/boot/vmlinuz
root=/dev/hdc5

ringwraith 11-25-2003 05:19 PM

and you ran lilo after making the correct entry in lilo.conf?

Kjetil4455 11-25-2003 05:19 PM

of cource

Kjetil4455 11-25-2003 05:29 PM

you post your lilo.conf to me please, maybe i'll discover i did something wrong.

Kjetil4455 11-25-2003 05:30 PM

(can't post mine, I'm in windows and I'm too lazy to reboot:P)

Kjetil4455 11-25-2003 06:16 PM

here it comes;

# 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
# DOS bootable partition config begins
other = /dev/hda1
label = Windows
table = /dev/hda
# DOS bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/hdb1
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/hdc5
label = Debian
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends

kasperhans 11-26-2003 12:25 AM

try first root then image and also maybe just renaming the debian boot image if nothing else helps

Locura 11-26-2003 01:38 AM

I had this problem once before when experimenting with multiple distros. The solution was to put a copy of the kernel image in the /boot/ directory of my slackware setup. I don't know why it worked, but it did.

Kjetil4455 11-26-2003 06:58 AM

To be honest, i've allready tried that. and.. i guess it worked. but i find that as an cheap sulution. i want to really fix it. any one?

a slacker 11-26-2003 07:26 AM

Try mounting your debian partition under slack (call it /mnt/debian). Then run:

mount /dev/hdc5 /mnt/debian

and it will mount your debian partition. Then change your lilo.conf to look like this:

# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/hdb1
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 = /mnt/debian/boot/vmlinuz
root = /dev/hdc5
label = Debian
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends

Then run lilo again and reboot. It should then boot your debian kernel correctly

Kjetil4455 11-26-2003 07:27 AM

Quote:

Originally posted by kasperhans
try first root then image and also maybe just renaming the debian boot image if nothing else helps
dude, no. that didn't work either. lilo gave me some nasty error. that's not how it's supposed to be lined.

Kjetil4455 11-26-2003 07:48 AM

Quote:

Originally posted by a slacker
Try mounting your debian partition under slack (call it /mnt/debian). Then run:

mount /dev/hdc5 /mnt/debian

and it will mount your debian partition. Then change your lilo.conf to look like this:

# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/hdb1
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 = /mnt/debian/boot/vmlinuz
root = /dev/hdc5
label = Debian
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends

Then run lilo again and reboot. It should then boot your debian kernel correctly

That wont work, because the Debian disk is mounted under bootup of slackware.


All times are GMT -5. The time now is 10:40 AM.