Debian and Slackware Dual Boot

swampdog2002 · 02-01-2008, 09:48 AM

I am contemplating setting up a dual boot system on one of my computers that would have both Debian 4.0 and Slackware 12 on it. I was just wondering which distribution should I install first to avoid too many problems for this. I know that Debian uses grub by default, and I am not certain that, if I installed Slackware first, whether the grub boot loader installed by Debian would "see" Slackware and automatically add an entry to the boot menu. Any suggestions on this are appreciated.

AtomicAmish · 02-01-2008, 10:26 AM

I have been running Slackware exclusively for several months, and just yesterday added Debian. I am currently upgrading Debian stable to testing.

Months ago, I installed LILO to the MBR and also the Slackware partition. I plan to chainload LILO from Debian's GRUB, which is now in the MBR.

The reason I'm doing this is because the Debian installer surprisingly detected Slackware and suggested adding it to GRUB, but it later gave me a kernel panic when I booted into Slackware.

So, that's my suggestion: Slackware first; LILO to the partition; then Debian and its GRUB to the MBR; modify Debian's GRUB to boot Slack's LILO.

If you're not familiar with it, chainloading is easy. Just be careful with the partition values - i.e., the first partition is called 0 in GRUB, the second is called 1, etc.

Code:

title Slackware 12.0
root (hdx,x)
rootnoverify (hdx,x)
chainload +1

Edit: Given that you already have Slackware installed, it would be easier to just install Debian on SUSE's partition. There's no need to re-install Slackware. Debian's GRUB may or may not pick up Slackware, but you can just modify its /boot/grub/menu.lst after it's installed.

gnashley · 02-01-2008, 11:52 AM

I'd suggest the other way around -debian first then slackware. GRUB is much easier to setup and use for multi-boot than lilo. But, if yuo are more familiar with setting up lil, then install slackware first and then debian. Neither bootloader will 'automatically' see the other distro and create an entry for you, but grub is much easier. You could even mount the partition where the grub menu.lst file is after installing slackware and before rebooting to add the entry for the new slackware installation.

swampdog2002 · 02-01-2008, 01:24 PM

AtomicAmish, the computer that I wish to dual boot with Debian and Slackware only has Slackware 11 installed currently. I have SuSE (well, multiple SuSE installations anyway) on other systems. I actually prefer LILO, so if I installed either one and then just used this bootloader, I should be able to add the required entries accordingly. The only concern that I would have would be that I am not too familiar with Debian's structure needed to boot, such as initrd entries and such. What I can possibly do is take the existing lilo.conf file on the machine which currently has Slack 11 on it and then compare it to the lilo.conf file on the system once Debian and Slackware are installed. I believe that there is an option during Debian setup to specify to use LILO instead of grub, so I'll see what happens. Thanks for the suggestions so far.

syg00 · 02-01-2008, 03:44 PM

As suggested above, use chainloading - means you get two loader menus, but you can always hide them or use short time-outs.
Put whatever you are most comfortable with in the MBR, then do the other install(s) with the loader they ship installed to the partition.
Then just chainload - no need to worry about (and continually update) boot-loader entries.

KISS.

allend · 02-03-2008, 05:07 AM

Probably too late, but this describes what worked for me.
http://www.linuxquestions.org/questi...light=64studio

duryodhan · 02-03-2008, 10:00 AM

Quote:

Then just chainload - no need to worry about (and continually update) boot-loader entries.

KISS.

I second this .... only if everyone did this, half of the booting problems wouldn't come. Whenever you install a new distro , don't let it touch your mbr, and ask it to install its bootloader to the root partition.

jowa45 · 02-05-2008, 05:26 AM

Hi all,

Would someone mind explaining the chain load a little more explicitly.

My situation is like this.
On one of my machines I have Slackware 12 default installation
lilo mbr hda1. Works fine.

On hdb1 I have been building embedded clfs x86.
Embedded clfs is still under development and the bootloader section is
left to the readers imagination. So I dont have one but would like to
use grub.

At first I would like to boot my build from Slackware.
Then boot itself.

Can I boot from Slackware without a bootloader in embedded?
Must I mount embedded somewhere in Slackware?
What would lilo stanza look like?

I have read a lot about booting a system called "other" from lilo but not much
about a Linux system.

John

duryodhan · 02-05-2008, 06:15 AM

install grub to the mbr of hdb.

lilo entry would look like

Quote:

label="Second HDD - embedded linux "
other=/dev/hdb

grub would just boot the linux in the embedded system

Quote:

title embedded
root (hd1,0)
kernel /boot/vmlinuz root=/dev/hdb1

root (hd1,0) for hdb1.