GeneralThis forum is for non-technical general discussion which can include both Linux and non-Linux topics. Have fun!
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.
I think this question should be fairly easy for someone out there.
I have a Dell precision running RH7.2 with a SCSI HD.
I installed a second HD which is an IDE drive. To do this I moved the CD burner that was the master on the second IDE controller to slave and put the IDE HD on as master. I set the jumpers not allowing cable select. I set the HD sequence in the bios to the SCSI HD and booted. The system boots fine and apparently recognizes the both the IDE drive and the CD burner. That according to /proc/ide and /var/dmesg. However, when I try 'fdisk /dev/hdc" I get the message "unable to open /dev/hdc".
After reading through a lot of threads I figured the problem was in the lilo.conf. I amended the append line to read "hdc=ide" instead of "hdc=ide-scsi" and rebooted. No luck. I still got the same fdisk error message. The then deleted the line altogether and rebooted. Again no luck. I still think it is a lilo problem but I'm stuck. Any help would be appreciated.
You're still booting the kernel with the argument that makes it treat /dev/hdc as a SCSI device. The kernel can emulate scsi over ata for the cdrw, but not for the hard drive, that's why its flipping out. Change both of those boot arguments to hdd instead of hdc, so it subjects the cd-rw to the scsi treatment.
I have RH7.2 which is still using lilo. I edited the lilo.conf file and rebooted but that didn't work. Do I need to rerun lilo? I was hesitant to do that. BTW the images in lilo.conf are RO. Should I change them to RW?
1. Yes you need to re-run lilo, if it detects errors in the conf file it won't over-write the MBR, so don't sweat it... lilo is hard to break. I re-run lilo a lot, but then again I have about 14 kernel images at any given time so I always usually keep one good option around.
2. No the kernel remains read-only during the boot process, this is a good thing.