[SOLVED] What to add to lilo for this situation...
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.
Hi gang. I need a little help figuring out how to put my sdb into my lilo.conf on my sda. The problem is, sda is Slackware 14.0 x86 and sdb is Slackware 14.1 x86_64 and thus is using the elilo/grub2 and the uefi crap on the MOBO to boot up.
What exactly do I add to lilo to be able to choose between the two hdd's when booting?
Are you planning on using EFI or legacy boot? You'll have to decide which system you're going to use.
However, another problem that you may or may not have observed is the type of partition layout of your disks. If you use EFI with elilo, then both of your disks must have GPT partitions. If you plan on using regular lilo, then they must be MBR formatted. I don't think you can create a hybrid of the two.
Yeah, not long after I rebooted into my 14.0 hdd, I realized there's just not going to be any way. That means any time I boot into the *other* hdd, I have to fiddle with the BIOS settings. <sigh> Oh well, life in the woods, heh. Thanks for responding and letting me know my fears were well founded, angryfirelord.
It looks like gdisk will try to convert it when you first launch it. You'll just have to squeeze a BIOS boot partition (EF02) into the MBR. I don't know if you'll need an EFI partition on it (EF00) afterwards. I'll have to look at my partitioning setup later. But if you're not using that as the primary boot disk, you probably won't need it. You just have to make another menu entry and point elilo to the correct disk.
I think I'd better stay with what I have working, heh heh. That sounds like a lot more toruble than making a quick change in the BIOS any time I want/need to get to the other hdd. Thanks though for the idea.
I think I'd better stay with what I have working, heh heh. That sounds like a lot more toruble than making a quick change in the BIOS any time I want/need to get to the other hdd. Thanks though for the idea.
why not install the second hard drive as the primary drive install the O/S
you may or may not need to edit the /etc/fstab change all the sda? to sdb?
move the drive back to being the secondary replace the primary drive
and use the BIOS boot menu F12 key on start up when you want to run the second O/S
Actually, I've not been too impressed with the x86_64 part of it all. For one thing, it is almost 2 hours *slower* when doing my seti@home stuff than on my x86_32 14.0 hdd.
Also just found out I'll have to do the whole multilib junk and hope that would be what's needed to get my Brother printer to even be seen much less work, like it does on the 14.0 hdd (right now on the 14.1 hdd, cups isn't even running when I boot into it for some reason).
I've not found anything yet that has made me think the kde 4.10.<whatever> on 14.1 is any better than whatever version it is on my 14.0 hdd. It still works just fine, like Slackware just does, but any extra troubles I have to go through just to get an app to work or hardware to work just isn't justifiable enough to *me* to run it. I think I'll just change it back to my 'storage' drive that it was before I experimented with an x86_64 system to see if the fuss about it was actually worth anything.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.