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.
I'm gonna take a break from this project for a few days, So I decided to post my
question, and hope someone answers it before I get the energy to continue.
I have slackware 10 on hda1
lilo on mbr of hda - slackware works great (AS USUAL )
I have suse 9.1 on hdb1
Grub on mbr of hdb - works fine if I physically disconnect hda
(or change the boot sequence in the MB bios.)
I can not get lilo to either boot suse or pass control over to grub.
If you boot 2 versions of linux, 1 on hda and the other on hdb,
PLEASE post your lilo.conf.
I've managed to get Mandrake 10 and slackware working together nicely (along with XP and ME)
what I had to do because modules and stuff were loading from drake when starting slack:
First, the main (Mandrakes) lilo is on MBR.
slackware has its own lilo on its own root partition, which has no delay (boots straight to slack)
and add this partition as 'other' in the main lilo.
what I also did, but sent the system a bit iffy was have a /mnt/slack/ in mandrake to get to my Slack root., and a /mnt/drake so I could read my Drake root in Slack. I think something happened to the permissions though and thing went strange, so now they just share the /home partition and I removed the /mnt's
Distribution: SlackWare 10.1+, FreeBSD 4.4-5.2, Amiga 1.3,2.1,3.1, Windors XP Pro (makes a fair answering machine)
Posts: 287
Rep:
I "solved" this with a little trickery....
Dragon (see below) has 6 hard drives. Each drive is a different version of a Slack based install and each drive has its own kernel.
hda is the master/rescue install. It also controls the boot of ANY of the other installs and drives. hda carrys all the kernels by proxy of the other installs.
hda has the lilo.conf and passes the root off to the other drives
Well, I have had no luck so far - but thanks to those who replied for the suggestions. I currently have
2 sections trying to boot suse - both kinda going different directions, and both being modified a number
of times from what is seen here.
1-
# Linux bootable partition config begins
other = /dev/hdb
label = SuSe
boot-as=0x80
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends
I am sure someone is doing this using lilo. (somewhere in the world) - If you have the solution or an idea,
please let me know. I have stumbled upon anather issue, but I would like this one resolved first (since I am
already working on it).
# Linux bootable partition config begins
# boot = /dev/hdb #overwrite MBR of hdb
# disk = /dev/hdb #tell how hdb will look like
# bios = 0x80 # the bios will see it as the 1st drive
# delay = 0 # don't wait
# vga = 314 # Suse's grub uses vga = 0x314 so I put this here
# image = /boot/vmlinuz # where to find the kernel
# initrd = /boot/initrd # Suse uses initrd and this is its location
# root = /dev/hda1 # Use hda1 here becuase of the 0x80 line above
# label = SuSe # what this is called
# read-only # as usual
# Linux bootable partition config ends
NOTE:If I remove the 'boot' and 'disk' lines, I then get an error running lilo that
says "/boot/initrd is not found" - obvoiusly 'cause I am running lilo from hda and
the initrd is on hdb at the time.
This is getting worse every time I try it. Now when I run lilo (to save my changes to the mbr),
if the "boot" or the "disk" option is first, I get a "syntax error on line xx" message.
Any more ideas/help would be appreciated. I hate to be a pain, and rehashing the same issue,
but this seems like it would be possible... but I am having no luck so far...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.