Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
dup2 "Bad file descriptor" in essence means "cant check, cant mount, cant read". Processes spawned tru rc.sysinit (the boot script) can't get file descriptors off of /proc, cuz the partition /proc is on isnt fsck'ed, so /proc can't be mounted in read-write mode.
try booting off the install cd with "linux rescue" or use a bootfloppy, or use a bootdisk like tomsrtbt.
run fsck with the -f (force) on /dev/(all partitions).
if any errors come tru, plz tell us exactly what.
*just my curiousity, did u have a good security scheme on ure box?
I'm also getting this on about 10 of my machines. Is it hardware? I have a auto update script running which compares RPM's on the local system to updates.redhat.com and if updates.redhat.com is newer it does a rpm -U --nodeps package name. Could this be a problem?
Here's my quick fix for this but it sucks because it keeps happeneing again and again.
boot off toms boot disk
mount /dev/hda7 /mnt (hda7 = / partition on my machine)
mknod null c 1 3
chmod 0666 null
if you have the redhat cd you can do this 2 by just gettign into the install and then pressing alt+f2 and it should bring you to a sh term.