FedoraThis forum is for the discussion of the Fedora Project.
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 have the same error thanks to my 'efforts' last night!
Hansi, Woessey - Did the you add anything new like I did, or did it just happen on the first boot after the install?
My story.. I have been running FC3 for a few weeks (far from perfectly) and then yesterday decided to try to get it working better. Obviously, I made a mistake somewhere!
This is what I did -
1. Install the ATI Rage 200 driver (8.14.13) for X.Org 6.8, and run flxrconfig utility for said driver.
2. Install yum updates to the following packages (the ones I can remember)
..that's all I can remember. There was also a couple of the more general libraries, but I'm at work now, not home and don't have notes here.
Interestingly, I can hit Ctrl-C when the systems appears to stop at "configuring kernel parameters" and it enters runlevel 5. From there, the boot continues (or tries to) but can't 'touch' a couple of files (kudzu and syslog from memory) because the file system has loaded read-only. After that it halts again whilst trying to start the system logging daemon.
I will try to bring the system up in single-user mode (that's runlevel 1, right?) when I get home tonight, and see what I can find out from there. Not really sure what I'm looking for, but my first stop will be demsg, then var/log/messages (after I check that the kernel is still configured to log there).
Any other hints would be appreciated!
Last edited by BadDoggie987; 07-29-2005 at 04:59 AM.
If your system uses GRUB, you can change the boot runlevel by
pressing the `e' key to edit the boot configuration. append the
runlevel to the end of the boot command as shown:
kernel /vmlinuz ro root=/dev/hda1 5
Last edited by musicman_ace; 07-30-2005 at 05:23 AM.
I still don't understand how to do this stuff. I am extremely new to Linux. I know absolutely nothing about any of the commands. If you are going to tell me what to do, you need to tell me exactly what to type and when to type it. I'm sorry that I am this dumb about everything. I'm just trying to learn everything I can.