LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices


Reply
  Search this Thread
Old 02-21-2014, 12:14 AM   #1
tb75252
Member
 
Registered: Oct 2010
Distribution: Slackware 14.2 (64-bit)
Posts: 156

Rep: Reputation: Disabled
Adding Second Distro To LILO


I am using Slackware 14.1 64-bit with the KDE desktop environment. LILO is installed in the MBR and root is in sda1.

Just for fun I decided to install the 32-bit version of Slackware 14.1, too. Root is in sda5 and so is LILO (superblock of sda5).

When I boot up, LILO only shows an entry for Slackware 64-bit. How do I add Slackware 32-bit to LILO?
 
Old 02-21-2014, 12:58 AM   #2
itsgregman
Member
 
Registered: Jan 2008
Location: North Carolina
Distribution: Slackware 14.1
Posts: 199

Rep: Reputation: 59
you could try adding to lilo.conf

other = /dev/sda5
label = slackware32

Then as root type "lilo" without quotations to update lilo then reboot and see if you're able to chain load your other lilo.

Last edited by itsgregman; 02-21-2014 at 01:19 AM.
 
Old 02-21-2014, 01:21 AM   #3
tb75252
Member
 
Registered: Oct 2010
Distribution: Slackware 14.2 (64-bit)
Posts: 156

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by itsgregman View Post
you could try adding to lilo.conf

other = /dev/sda5
label = slackware32
table = /dev/sda

Then as root type "lilo" without quotations to update lilo then reboot and see if you're able to chain load your other lilo.
I'm not sure if you would need the table entry, I'd try it without it first and if it doesn't work add it and try again.
I am getting the following error message:
Quote:
Fatal: Partition entry not found.
 
Old 02-21-2014, 06:45 AM   #4
millgates
Member
 
Registered: Feb 2009
Location: 192.168.x.x
Distribution: Slackware
Posts: 840

Rep: Reputation: 380Reputation: 380Reputation: 380Reputation: 380
I don't think you need two LILOs. I would just add another entry to the MBR bootloader
Code:
image = /path/to/slack32kernel
  root = /dev/sda5
  label = slack32
  read-only
and reinstall lilo
 
Old 02-21-2014, 06:55 AM   #5
tb75252
Member
 
Registered: Oct 2010
Distribution: Slackware 14.2 (64-bit)
Posts: 156

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by millgates View Post
I don't think you need two LILOs. I would just add another entry to the MBR bootloader
Code:
image = /path/to/slack32kernel
  root = /dev/sda5
  label = slack32
  read-only
and reinstall lilo
Sorry but I am not much of an expert... How do I find the path to, and name of, my slack32 kernel?
 
Old 02-22-2014, 05:02 AM   #6
millgates
Member
 
Registered: Feb 2009
Location: 192.168.x.x
Distribution: Slackware
Posts: 840

Rep: Reputation: 380Reputation: 380Reputation: 380Reputation: 380
Quote:
Originally Posted by tb75252 View Post
Sorry but I am not much of an expert... How do I find the path to, and name of, my slack32 kernel?
The default path of the kernel in Slackware is, as far as I remember, /boot/vmlinuz. It will probably be a symlink to some other file in the same directory, but it shouldn't matter. However, the /boot directory of your 32bit Slackware is _not_ the one you see in your 64bit system (unless you have the same partition for /boot for both systems). So, mount the partition which contains the 32bit Slackware (in your case, I assume /dev/sda5) to some directory if it's not mounted already:

Code:
mkdir /mnt/slack32
mount /dev/sda5 /mnt/slack32
Now, the path to your 32bit kernel should be /mnt/slack32/boot/vmlinuz, so put that in the lilo.conf and run
Code:
/sbin/lilo
After lilo is successfully installed, you can safely unmount /dev/sda5 and remove the /mnt/slack32 directory.
 
Old 02-25-2014, 12:24 PM   #7
tb75252
Member
 
Registered: Oct 2010
Distribution: Slackware 14.2 (64-bit)
Posts: 156

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by millgates View Post
The default path of the kernel in Slackware is, as far as I remember, /boot/vmlinuz. It will probably be a symlink to some other file in the same directory, but it shouldn't matter. However, the /boot directory of your 32bit Slackware is _not_ the one you see in your 64bit system (unless you have the same partition for /boot for both systems). So, mount the partition which contains the 32bit Slackware (in your case, I assume /dev/sda5) to some directory if it's not mounted already:

Code:
mkdir /mnt/slack32
mount /dev/sda5 /mnt/slack32
Now, the path to your 32bit kernel should be /mnt/slack32/boot/vmlinuz, so put that in the lilo.conf and run
Code:
/sbin/lilo
After lilo is successfully installed, you can safely unmount /dev/sda5 and remove the /mnt/slack32 directory.
Thank you for your help! LILO seems to work fine now.
 
  


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
Strangle lilo behavior when adding new grub-default distro svar Linux - General 6 06-29-2008 11:03 AM
Adding to LILO JMJ_coder *BSD 1 03-09-2007 12:28 PM
Adding Debian to LILO? Ray2047 Debian 1 05-21-2006 07:13 AM
Are other distro's adding repositories so I can use yum for all my distro's? t3gah Linux - Software 4 03-21-2005 05:57 AM
Adding another Linux OS to lilo RoaCh Of DisCor Linux - Software 2 12-05-2004 07:11 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie

All times are GMT -5. The time now is 06:12 AM.

Main Menu
Advertisement
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
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration