LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
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 08-02-2009, 12:50 PM   #1
hitest
Senior Member
 
Registered: Mar 2004
Location: Prince Rupert, B.C., Canada
Distribution: Slackware, OpenBSD
Posts: 4,163

Rep: Reputation: 527Reputation: 527Reputation: 527Reputation: 527Reputation: 527Reputation: 527
Question Lilo set-up to dual boot Slackware 12.2 with Slackware64 -current?


Greetings!

This is probably an odd request.
I'm familiar with how to set-up a dual boot with Slackware and FreeBSD. Here is my present lilo.conf; I'm dual booting Slackware 12.2 with FreeBSD 7.2. My home partition is mounted on sda3, FreeBSD is installed on sda4.
I would like to give Slackware64 -current a try. I would like to install Slackware64 on sda4 (blow out my FreeBSD partition), then set-up a dual boot with Slackware 12.2 and Slackware64 -current.
I would be very thankful if someone could please suggest how to write the last portion of my lilo.conf such that I'm able to dual boot Slackware12.2/Slackware64 -current. I've googled this, but, am a bit unclear as to what format to use for lilo.conf.
Thank you for any and all replies.

Code:
# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/sda2
  label = Linux
  read-only
# Linux bootable partition config ends
# FreeBSD
other = /dev/sda4
table = /dev/sda
label = FreeBSD
 
Old 08-02-2009, 01:00 PM   #2
brianL
LQ 5k Club
 
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware & Slackware64 14.1
Posts: 6,963
Blog Entries: 52

Rep: Reputation: Disabled
Put Slackware64's lilo in its root, then add this to 12.2's lilo.conf:
Code:
other = /dev/whatever
  label = Slackware64
Then run lilo.
Probably similar to what you had before.
You must have been editing your post while I was typing mine.

Last edited by brianL; 08-02-2009 at 01:01 PM.
 
Old 08-02-2009, 02:09 PM   #3
hitest
Senior Member
 
Registered: Mar 2004
Location: Prince Rupert, B.C., Canada
Distribution: Slackware, OpenBSD
Posts: 4,163

Original Poster
Rep: Reputation: 527Reputation: 527Reputation: 527Reputation: 527Reputation: 527Reputation: 527
Thank you, brianL!
 
Old 08-02-2009, 02:35 PM   #4
MQMan
Member
 
Registered: Jan 2004
Location: Los Angeles
Distribution: Slack64 13.37
Posts: 535

Rep: Reputation: 36
Quote:
Originally Posted by brianL View Post
Put Slackware64's lilo in its root, then add this to 12.2's lilo.conf:
Code:
other = /dev/whatever
  label = Slackware64
Then run lilo.
Probably similar to what you had before.
You must have been editing your post while I was typing mine.
That will only work if the Slack, on /dev/whatever has lilo installed, so that the 1st lilo boots the 2nd.

Do you run lilo from the MBR. If so, then from you current system, you need to mount /dev/whatever, and set the lilo entry for Slack64, the same as for your normal Slack, but use the full path, from the mount point, to locate the Slack64 kernel.


Code:
# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/sda2
  label = Linux
  read-only
image = /mount/boot/vmlinuz
  root = /dev/whatever
  label = Slack64
Cheers.

Last edited by MQMan; 08-02-2009 at 02:37 PM.
 
Old 08-02-2009, 02:39 PM   #5
brianL
LQ 5k Club
 
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware & Slackware64 14.1
Posts: 6,963
Blog Entries: 52

Rep: Reputation: Disabled
Yes, I meant if 12.2's lilo was in the MBR. I've got it set up as I mentioned in my previous post, and it works.
From my 12.2 lilo.conf:
Code:
# Linux bootable partition config begins
image = /boot/vmlinuz-generic-smp-2.6.27.7-smp
  initrd = /boot/initrd.gz
  root = /dev/sda2
  label = Linux_G
  read-only
# Linux bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz-2.6.27.7-smp-custom
  root = /dev/sda2
  label = Linux_C
  read-only
# Linux bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/sda2
  label = Linux_H
  read-only
# Linux bootable partition config ends
# Slackware64
other = /dev/sda5
  label = Slackware64

Last edited by brianL; 08-02-2009 at 02:55 PM.
 
Old 08-02-2009, 03:09 PM   #6
MQMan
Member
 
Registered: Jan 2004
Location: Los Angeles
Distribution: Slack64 13.37
Posts: 535

Rep: Reputation: 36
Quote:
Originally Posted by brianL View Post
Yes, I meant if 12.2's lilo was in the MBR. I've got it set up as I mentioned in my previous post, and it works.
From my 12.2 lilo.conf:
Code:
# Linux bootable partition config ends
# Slackware64
other = /dev/sda5
  label = Slackware64
Maybe I didn't make myself clear. The above would only work, if you installed LILO in the /dev/sda5 partition as well, when installing Slack64, in addition to the LILO in the MBR. That way, the LILO in the MBR then loads the LILO from /dev/sda5.

The method I proposed uses only one copy of LILO, in the MBR, and can boot as many other copies of Slack, in different partitions, as needed. You just have to mount them, before running LILO.

Cheers.
 
Old 08-02-2009, 03:12 PM   #7
brianL
LQ 5k Club
 
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware & Slackware64 14.1
Posts: 6,963
Blog Entries: 52

Rep: Reputation: Disabled
Quote:
Originally Posted by brianL View Post
Put Slackware64's lilo in its root
That's what I said in my previous post.
 
Old 08-02-2009, 04:20 PM   #8
hitest
Senior Member
 
Registered: Mar 2004
Location: Prince Rupert, B.C., Canada
Distribution: Slackware, OpenBSD
Posts: 4,163

Original Poster
Rep: Reputation: 527Reputation: 527Reputation: 527Reputation: 527Reputation: 527Reputation: 527
Thanks, brianL. Your method worked perfectly. Just finishing installing Slackware64 -current over my FreeBSD partition. I'm posting this from Slackware64 -current. KDE 4.2.4 is very sweet indeed. Now to go finish-up setting up stuff
 
Old 08-02-2009, 04:25 PM   #9
brianL
LQ 5k Club
 
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware & Slackware64 14.1
Posts: 6,963
Blog Entries: 52

Rep: Reputation: Disabled
OK, have fun!
I wasn't too keen on KDE4 when I first saw it, but I'm getting to like it.
 
Old 08-02-2009, 07:45 PM   #10
hitest
Senior Member
 
Registered: Mar 2004
Location: Prince Rupert, B.C., Canada
Distribution: Slackware, OpenBSD
Posts: 4,163

Original Poster
Rep: Reputation: 527Reputation: 527Reputation: 527Reputation: 527Reputation: 527Reputation: 527
Quote:
Originally Posted by brianL View Post
OK, have fun!
I wasn't too keen on KDE4 when I first saw it, but I'm getting to like it.
Just updated the system with slackpkg. I'm having fun.
 
Old 08-02-2009, 08:59 PM   #11
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 1,913

Rep: Reputation: Disabled
I like BrianL's method just fine, but you can also dual-boot by using the complete mountpoint of the alternative partition for your root and image locations. IOW, if your 12.2 partition is the one from which you always will run lilo, you can do this:

Code:
boot = /dev/sda

...

image = /boot/vmlinuz
  root= /dev/sda1
  label = 12.2
  read-only

image = /mnt/sda2/boot/vmlinuz
  root = /dev/sda2
  label = 13.0_32bit
  read-only

image = /mnt/sda3/boot/vmlinuz
  root = /dev/sda3
  label = 13.0_64bit
  read-only
Ultimately, this is less flexible than what BrianL recommended, so his is a better solution, but whatever works for you is fine :-)

Last edited by rworkman; 08-02-2009 at 09:00 PM.
 
Old 08-02-2009, 09:08 PM   #12
niels.horn
Senior Member
 
Registered: Mar 2007
Location: Rio de Janeiro - Brazil
Distribution: Slackware64-current
Posts: 1,004

Rep: Reputation: 89
And then there is also the possibility of creating a small (~200MB) partition for /boot and put all your kernels there.
This is the setup I use.
Actually, I mount /boot on /dev/sda1, where I keep the kernels for Slackware-stable, Slackware-current and Slackware64-current.
The /home partition is shared between them as /dev/sda6 and /root is either /dev/sda3, /dev/sda4 or /dev/sda5

But, as Robby said, whatever works for you is fine
 
Old 08-02-2009, 09:30 PM   #13
hitest
Senior Member
 
Registered: Mar 2004
Location: Prince Rupert, B.C., Canada
Distribution: Slackware, OpenBSD
Posts: 4,163

Original Poster
Rep: Reputation: 527Reputation: 527Reputation: 527Reputation: 527Reputation: 527Reputation: 527
brianL, Robby, niels.horn,

Thank you very much for your posts, it is appreciated! I'm book marking this thread for the next time I set-up a dual boot with Slackware stable and -current.
Everything is working well.
 
Old 08-03-2009, 02:30 PM   #14
Stroker
Member
 
Registered: Dec 2006
Location: The Nature Coast
Distribution: Slackware 01001101
Posts: 83

Rep: Reputation: 18
I'm going to give 64 a try and this thread has been very helpful. I have some questions about the /home partition.

Quote:
Originally Posted by niels.horn View Post
The /home partition is shared between them as /dev/sda6
Can't this cause conflicts? I'm especially referring to dot files, like kde configs. What happens to them when you are booting two different version, e.g. kde3.x and kde4.x on the same /home?

I'm thinking I'd like a separate clean /home for testing 64 with kde4.

Any thoughts or advice appreciated.
 
Old 08-03-2009, 02:36 PM   #15
brianL
LQ 5k Club
 
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware & Slackware64 14.1
Posts: 6,963
Blog Entries: 52

Rep: Reputation: Disabled
I have to say it's not my method originally - think I got it from an article by Saikee. It's a useful method if you're trying out distros where the kernel is likely to be updated.
 
  


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
Is PKG_CONFIG_PATH set wrong in slackware64-current?? lumak Slackware 20 09-15-2009 02:07 PM
Slackware64-current : can't have lilo updating the boot loader after kernel upgrade Didier Spaier Slackware 3 07-21-2009 08:00 AM
How to set up dual-boot in LILO for Slackware 10.0 Shockshell Linux - Newbie 3 02-12-2005 09:39 PM


All times are GMT -5. The time now is 05:29 AM.

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