Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with 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.
Running RedHat 6.2 on a PC using a boot manager to coexist with Win98. Windows is running on a single IDE drive. Linux is running on a SCSI drive, with swap and an ext2 filesystem on two other SCSI drives.
I want to add another IDE drive to the system for Win98 use. But when I do, I can't get Linux to boot properly because the new IDE drive causes changes in the device numbering for the SCSI drives. What can I do to remedy this situation?
well i'd suggest using lilo instead, much nicer imho. also though you change your fstab file to use labels rather than partition numbers. using the e2label command you can call each linux partition by a set name, which you can then set in /etc/fstab
LABEL=/usr /usr ext2 defaults 1 1
so you don't need partition numbers, which will make it more flexible
Originally posted by jerrymc I'm using System Commander 2000.
I'm not familiar with System Commander 2000. See if it has a setup option that will allow you to see all the drives and partitions on your system. Make sure you have your new drive installed so that it can detect it. Then see if you can reselect your linux system.
The problem doesn't seem to be with System Commander. I get so far as to see LILO trying to start but it gets stuck. And I don't actually know that the device numbering is changing - that's an assumption.
So what do I need to do to /etc/lilo.conf to get it to boot properly? Is there a command to add to lilo.conf to make it more verbose? I need a clue as to what it's getting stuck on.
If I use the e2label command to create labels for my root and boot partitions, changing lilo.conf appropriately, how does this make a difference? Since the label is attached to a specific device, doesn't that still assume that the device doesn't change?
Could my problem have anything to do with the fact that the new IDE drive I'm trying to add is 14GB and my system BIOS doesn't go past 8GB without something like EZdrive?