LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 02-01-2008, 09:48 AM   #1
swampdog2002
Member
 
Registered: Jul 2005
Distribution: Slackware 12.2, 13.0, openSUSE 11.2
Posts: 397

Rep: Reputation: 33
Debian and Slackware Dual Boot - Which to Install First?


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.
 
Old 02-01-2008, 10:26 AM   #2
AtomicAmish
Member
 
Registered: Dec 2005
Location: East coast, USA
Distribution: Slackware 12.0
Posts: 139

Rep: Reputation: 15
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.

Last edited by AtomicAmish; 02-01-2008 at 10:34 AM.
 
Old 02-01-2008, 11:52 AM   #3
gnashley
Amigo developer
 
Registered: Dec 2003
Location: Germany
Distribution: Slackware
Posts: 4,746

Rep: Reputation: 458Reputation: 458Reputation: 458Reputation: 458Reputation: 458
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.
 
Old 02-01-2008, 01:24 PM   #4
swampdog2002
Member
 
Registered: Jul 2005
Distribution: Slackware 12.2, 13.0, openSUSE 11.2
Posts: 397

Original Poster
Rep: Reputation: 33
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.
 
Old 02-01-2008, 03:44 PM   #5
syg00
LQ Veteran
 
Registered: Aug 2003
Location: Australia
Distribution: Lots ...
Posts: 12,035

Rep: Reputation: 968Reputation: 968Reputation: 968Reputation: 968Reputation: 968Reputation: 968Reputation: 968Reputation: 968
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.
 
Old 02-03-2008, 05:07 AM   #6
allend
Senior Member
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 3,377

Rep: Reputation: 824Reputation: 824Reputation: 824Reputation: 824Reputation: 824Reputation: 824Reputation: 824
Probably too late, but this describes what worked for me.
http://www.linuxquestions.org/questi...light=64studio
 
Old 02-03-2008, 10:00 AM   #7
duryodhan
Senior Member
 
Registered: Oct 2006
Distribution: Slackware 12 Kernel 2.6.24 - probably upgraded by now
Posts: 1,054

Rep: Reputation: 46
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.
 
Old 02-05-2008, 05:26 AM   #8
jowa45
Member
 
Registered: Apr 2007
Location: Stockholm, Sweden
Distribution: Slackware11&12
Posts: 94

Rep: Reputation: 15
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
 
Old 02-05-2008, 06:15 AM   #9
duryodhan
Senior Member
 
Registered: Oct 2006
Distribution: Slackware 12 Kernel 2.6.24 - probably upgraded by now
Posts: 1,054

Rep: Reputation: 46
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.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Ubuntu 8.03a3 New Install: GRUB Error 21 after new dual-HDD, dual-boot install tvdxer Ubuntu 1 01-29-2008 01:08 PM
Dual-boot Debian and Slackware possible like this? nycace36 Linux - Distributions 1 10-10-2007 12:15 PM
grub issues: dual boot Debian i386 & Debian amd64 ErrorBound Debian 1 03-09-2007 07:41 PM
Install dual boot debian on raid1 issue linuxstarved Linux - Enterprise 1 01-12-2007 02:37 AM
Slackware install + dual boot with XP. Connected Slackware 1 04-24-2005 11:40 AM


All times are GMT -5. The time now is 07:41 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration