LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Home Forums Tutorials Articles Register
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 04-28-2011, 09:58 PM   #1
unclejed613
Member
 
Registered: Mar 2009
Posts: 352

Rep: Reputation: 32
13.37 lilo burped?


first, here's the drive setup
hda1 30G partition on a 40G PATA drive root partition for slack 13.0. showed up on slack 13.37 install as sdb1
hda2 10G partition for backing up files. showed up on slack 13.37 install as sdb2

sda1 30G partition on 1T SATA drive /home for both installs
sda2 950G partition on 1Tsata drive root partition for slack 13.37 install


the boot config for 13.0 reads:
Code:
# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/hda1
  label = Linux
  read-only
# Linux bootable partition config ends
the boot config for 13.37 reads:
Code:
# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/sda2
  label = Linux
  read-only
# Linux bootable partition config ends
the lilo config for 13.37 did not see a slack 13.0 install.
the machine still boots into slack 13.0

could somebody give me a clue how to set this up. is lilo for 13.37 going to see the PATA drive as hda or sdb?. i could probably get it to work by editing the lilo.conf for 13.0, because sda2 is the same in both installs..... it's also been a couple of years since i messed with dual boot, so i'll be reading the manpage for lilo.conf.
 
Old 04-28-2011, 10:44 PM   #2
aaket504
LQ Newbie
 
Registered: Apr 2004
Location: Ridgefield Park, New Jersey
Distribution: Arch
Posts: 13

Rep: Reputation: 0
It should be sdb1 then, because the installer and slack use the same kernel.
 
Old 04-28-2011, 11:09 PM   #3
unclejed613
Member
 
Registered: Mar 2009
Posts: 352

Original Poster
Rep: Reputation: 32
i'm trying to do a dual boot, so i don't lose any work (which is also the reason for the common /home partition) while i get apps and such installed in 13.37 that i'm already using in 13.0. so far i've managed to boot into 13.37 (by swapping boot first drives in cmos), but can't get into my user account because 13.37 reset my permissions to user 1000 and group 1000 so maybe i need to copy some stuff (like /etc/passwd) from the original install into the new one...

apparently the installer (13.37) sees sda as the first disk, and 13.0 sees hda (sdb) as the first disk, which is why lilo in 13.0 put the MBR of the PATA disk, and 13.37 put it on the MBR of the SATA disk, and it doesn't matter what the boot drive is set to in cmos, but the two different versions of slack see two different things for which piece of hardware is first

Last edited by unclejed613; 04-29-2011 at 12:18 AM.
 
Old 04-29-2011, 02:45 AM   #4
samac
Senior Member
 
Registered: Mar 2004
Location: Kirkwall, Orkney
Distribution: Linux Mint 20.3 - Cinnamon
Posts: 1,425

Rep: Reputation: 139Reputation: 139
I had this problem so I setup lilo to boot from the old install, and booted the new install from a usb-boot-pen which was created when I did the new install. Once I had the new install setup as I wanted it I ran lilo on the new install. If I want to access the old install I can boot from the install cd.

Not really a fix, but a reasonable work around.

samac
 
Old 04-29-2011, 03:39 AM   #5
Drakeo
Senior Member
 
Registered: Jan 2008
Location: Urbana IL
Distribution: Slackware, Slacko,
Posts: 3,716
Blog Entries: 3

Rep: Reputation: 483Reputation: 483Reputation: 483Reputation: 483Reputation: 483
this was documented by pat a long time ago on the 2.6.27 kernel Slackware 13.0 and was carried to the latest 13.37
read here for it
Quote:
7. IMPORTANT! *Before* attempting to reboot your system, you will need
to make sure that the bootloader has been updated for the new kernel!
First, be sure your initrd is up to date (if you use one). If you
use LILO, make sure the paths in /etc/lilo.conf point to a valid
kernel and then type 'lilo' to reinstall LILO. If you use a USB memory
stick to boot, copy the new kernel to it in place of the old one.

If you were using devices such as /dev/hda (IDE hard drive) with
Slackware 13.1, you will need to consider how to switch over to the
new /dev/sda type device names. See CHANGES_AND_HINTS.TXT for complete
instructions on how to do this. If you have not read this yet, now
is a great time to go look at that. Forget about step 8 and 9 and
just go complete that part of the upgrade and you'll be good to go.
Thank you Pat 13.37 solid

Last edited by Drakeo; 04-29-2011 at 03:43 AM. Reason: add herf
 
Old 04-29-2011, 06:21 AM   #6
unclejed613
Member
 
Registered: Mar 2009
Posts: 352

Original Poster
Rep: Reputation: 32
well i guess i can live with the "dual boot" method of changing the boot order in cmos then, at least for now, but i'm going to have to create a different user account in 13.37 because my common /home directory causes permission problems when i switch between versions unless copying the original /etc/passwd file to the new install will cure it.
 
Old 04-29-2011, 07:00 AM   #7
AlleyTrotter
Member
 
Registered: Jun 2002
Location: Coal Township PA
Distribution: Slackware64-15.0
Posts: 783

Rep: Reputation: 479Reputation: 479Reputation: 479Reputation: 479Reputation: 479
LILO

You can only have one MBR. Each time you run lilo you are altering the mbr

boot into 13.0
upgrade the lilo package to the version in 13.37

I would suggest the following in your lilo config file
Add this in the global section
boot = /dev/sda

Add after
# End LILO global section

# Linux bootable partition config begins
image = /boot/(your name for the 13.0 kernel)
root = /dev/sda1
label = Linux-13.0
read-only
# Linux bootable partition config ends
# Linux bootable partition config begins
image = /mnt/13.37/boot/(your name for the 13.37 kernel)
root = /dev/sdb2
label = Linux-13.37
read-only


Then alter your /etc/fstab to mount the 13.37 boot directory as /mnt/13.37/boot/(your name for your 13.37 kernel)
and mount it

run lilo
on reboot lilo should offer Linux-13.0 and Linux-13.37 as boot options

that should help
but please backup anything that is valuable

using the same username & password in each system and a common home will work but 2 different versions of KDE will not

This is how I sextupple boot
But I am not good at explaining myself

john

Last edited by AlleyTrotter; 04-29-2011 at 07:20 AM. Reason: forgot to add root =
 
Old 04-29-2011, 08:17 AM   #8
bonixavier
Member
 
Registered: Sep 2010
Distribution: Slackware
Posts: 320

Rep: Reputation: 69
If I may suggest another solution, boot from the install CD / DVD of 13.37.* When you're done, mount /dev/sda2 in /mnt. Mount proc and dev into /mnt/proc and /mnt/dev and chroot into /mnt. When you're there, mount 13.0's partition somewhere, like /mnt/hd.

Then you open lilo.conf. You need to know which hd gets called first by the BIOS. If it's the 40GB drive, add this:
Code:
boot = /dev/sdb
If it's the 1T drive, replace sdb with sda. Then, add the two entries. You have to use the temporary mount point as the reference for lilo or it will fail, so it will be something like this:

Code:
image = /boot/vmlinuz
  root = /dev/sda2
  label = Linux
  read-only

image = /mnt/hd/boot/vmlinuz
  root= /dev/sdb1
  Label = Slack
  read-only
Then you run lilo. This will update your MBR and will add both Slacks to the menu. Then you exit chroot and reboot. Let us know if it works.

* I don't know if 13.0's lilo will boot 13.37.
 
  


Reply



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
trying to update lilo on my usb hdd tells me /etc/lilo.conf wasn't found daweefolk Slackware 8 04-23-2010 01:20 AM
[SOLVED] Before Install: Slackware over Ubuntu (Grub to LILO), Dual w/Vista: LILO question Ubunoob001 Slackware - Installation 3 03-01-2010 03:01 PM
[SOLVED] LILO fails when run from live CD after installing Slack (skipped LILO during setup) sysfce2 Linux - Newbie 7 08-04-2009 12:16 AM
Switching from grub to lilo, messed up Lilo.conf, rescuing via Knoppix. SonicGT Debian 2 08-21-2005 01:15 PM
Lilo lost, Install disk failing to restore Lilo on dual boot? Dobie Linux - Newbie 2 05-05-2004 05:00 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 08:23 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
Open Source Consulting | Domain Registration