SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Well, here is problem on computer number one. I used to be a fairly hard-core devotee of Linux in the early 90s (kernel numbers < 1.0) but having not used UNIX of any sort in about 8 years, seem to be struggling with just about everything.
After hearing all this hoopla over Redhat, I installed Redhat, only to decide that Redhat _sucks_, if for no other reason than that those little redhat wearing fools thought they were being clever by violating every single UNIX convention ever _written_.
Back to slackware for me.
So, I did a couple of things:
Added a new hard drive, as, /dev/hda. (hda1 is /root, hda2 is swap)
Old hard drive was reformatted and mounted to /home as /dev/hdb1.
After slackware v10.0 install, I can boot from a floppy fine, but cannot boot from the hard drive. All that happens is grub comes up as "Grub" and the system hangs. So, I guess the brilliant boys at Red Hat wrote Grub into the MBR of /dev/hdb.
Why my computer boots to that, I don't know, but I think that is what's happening. I've installed LILO to /dev/hda (correctly, I think) but it just isn't happening.
Does anyone know how to fix this? My thinking is I need to clear the MBR on /dev/hdb (am not quite sure how to do this) and then install LILO to /dev/hda (but I think that's already done.)
something doesn't sound right. have you checked your BIOS, jumper settings, and cabling to make sure the hard drives are set up properly (master/slave on IDE1, master/master on IDE1/IDE2, etc.) ?
if that's okay, then what i would do is remove hdb, boot to hda, with the floppy disk if necessary, rerun lilo installing it to the MBR of hda, then shut down, add hdb again, and try to boot. once i was booted again with both drives, i would overhaul hdb just to clean everything off it. that should work, if not post back.
Originally posted by t-peters1975 Does anyone know how to fix this? My thinking is I need to clear the MBR on /dev/hdb (am not quite sure how to do this) and then install LILO to /dev/hda (but I think that's already done.)
I don't think /dev/hdb MBR has anything to do with it. If your BIOS points to /dev/hda as the boot disk, /hdb MBR never even comes into play.
Rather, make sure your lilo was correctly set up in /etc/lilo.conf (post it if you dont mind.)