Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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 trying to install Slackware 8.1 onto a secondary slave HD (hdd in this case). Slack setup will only allow installation of LILO onto the MBR of the first HD (the master I assume), so I decided to install it using
/sbin/lilo -M /dev/hdd
It says in the man pages that this won't disturb the primary partition table, but, guess what, I did it twice and both times the partiton table disappeared from hdd.
I suppose I could just disconnect the master HD when I install next time, but this is bugging me now. Can anyone help me get LILO on the MBR of hdd from the command line?
Why don't you want LILO on the primary hard drive? It's a boot manager, and you almost certainly want it on the primary hard drive, so you can boot from it. I'm pretty sure that if you don't want it on the primary drive, you don't want it at all.
Sorry, should have made myself more clear. The slave HD is from my tablet PC and needs to have LILO on the MBR so it will boot when I put it back in. I already have another boot manager on the master HD.
Do you know the answer to my original query? Why does the partition table get wiped when I install LILO?
Yes Dalek, at the moment I'm trying to inflate my lifejacket. The problem with the machine I'm putting the HD back into is that it doesn't have a CD or floppy drive (there's a USB slot but BIOS doesn't support booting from USB devices) so the only option is to have the drive bootable when I put it back in. Very irregular I know, and I'm certainly into uncharted waters as far as my limited knowledge goes.
Say I do the Slack install with the master HD disconnected and run through the entire setup. Will the HD work when I put it in the tablet PC? I know that in the original setup the HD was hda, but Slack has a tendency to see any HD on my desktop system as hdc+ - it puts the two CD drives in as hda & b. Would changing the IDE channels on the CDs and HDs make a difference (I think CDs are on channel 0, HDs on 1)?
Failing that, if Slack is installed on the HD as hdc, will there be problems when I put it back in the tablet?
That may work. If not you may have to boot from a Linux floppy and make a change or two.
I would do this. Remove the drive, windoze drive, and put in the drive you want Linux on as the Primary Master. Install Slackware and such then put the drive in the other system and return the windoze drive back to its proper place.
Done that way lilo, or grub, and the fstab files should be correct and your MBR will not be messed with on the windoze drive either. Don't forget to change your BIOS when you change the drives. It may get and do a bit of and you may a bit.
Did that make sense? I just don't know how it will work if you compile the kernel and the machines are really different.
Dare i say you are going to have problem if you install the OS as /dev/hdd and then move it back to the tab PC... the disk will then be visable as /dev/hda
The partitioning and filesystem tables will all be messed up.... best bet (if you can) is to install with the hdd in the tab pc as this will also configure the graphics and other devices... also the partitions would work correctly. I can talk you through moving from /dev/hdd to /dev/hda but it is better (in this case) not to have to.
If you are unable to use the tab pc to do the actual install, I would suggest installing it's hard disk as /dev/hda (primary master) on a donor PC and install from there...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.