Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's 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.
as I could not finish my linux properly (it seemed like my hole system was hanging, no process would start, I could not log in to any console), I had to press "Reset". During the re-boot, after trying to enter runlevel 5, it now says:
INIT: ld "1" respawning too fast: disabled for 5 minutes
INIT: ld "6" respawning too fast: disabled for 5 minutes
INIT: ld "x" respawning too fast: disabled for 5 minutes
Well, I waited for five minutes, and it showed the same again. Does anyone have an idea what happened, or (much better) how I can fix it?
Hard to say w/o a proper view on the system, but the "spawning to fast" usually involves a process invoked from init (like mgetty) being unable to write to a device like /dev/tty or /dev/log (syslog) which could happen if the root partition is mounted read-only (maybe due to fsck problems) or the node has somehow been destroyed, or wasn't made at all (aborted install?).
If you're totally unsure if the install did hang at 50,75 or 99% IMO it would be better to simply reinstall, just to be sure. Else boot in rescue mode, check if the disk mounts cleanly, and if it mounts ok in read/write mode try if running the makedev script in /dev helps. Since the disk prolly didn't mount in read/write mode, it's possible /var/log/(dmesg,messages) doesn't contain a clue, but its always good to check the logs as a starting point. Also, since it's an install, maybe there are some logs in /tmp.
To run in recue mode use either the cdr, add "init=/bin/sh" at the bootprompt, or "linux single", depending on config/distro. This will drop you in single user mode to make repairs etc etc.
After booting in rescue mode, I looked in /var/log/messages. The (in my opinion) most important things it says are:
init: trying to re-exec init
failed to start X-Server several times, disabling display:0
init: Id "x" respawning too fast
The last two entries are logged in the same second. 15 seconds later there is:
init: Id "4" respawning too fast
And that is the last entry there. Maybe I should mention that a few minutes before my system crashed, I updated my glibc from 2.2 to 2.4, but something was wrong with the glibc rpm, so that I could only update glibc-common and glibc-devel, but not the actual glibc rpm. Probably this has something to do with it.
dmesg didn't show much information, only:
EXT2-fs warning: mounting unchecked fs
So I ran e2fsck, but it didn't help.
Well, I hope this is not too much irrelevant information. Maybe somebody has any clue. If not, this might be the right moment to update to RH 7.2.