SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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.
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.
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.
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
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.
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:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.