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.
The installation was great. The problem came when FEDORA ask me to select a monitor. after selecting a generic LCD, and clicked fot the next step, The screen became black, as if the monitor were turn it off.
I had to reboot the PC.
Now, Fedora booting proccess seems to be normal, but during the proccess, again, the black screen comes, and there's no other alternative than turn OFF the PC.
what user did you log in as? You probably need execute as root for init would be my guess (login as root or sudo). I snippet from init's manual pages follows:
Init is the parent of all processes. Its primary role is to create
processes from a script stored in the file /etc/inittab (see init-
tab(5)). This file usually has entries which cause init to spawn get-
tys on each line that users can log in. It also controls autonomous
processes required by any particular system.
A runlevel is a software configuration of the system which allows only
a selected group of processes to exist. The processes spawned by init
for each of these runlevels are defined in the /etc/inittab file. Init
can be in one of eight runlevels: 0â6 and S or s. The runlevel is
changed by having a privileged user run telinit, which sends appropri-
ate signals to init, telling it which runlevel to change to.
Runlevels 0, 1, and 6 are reserved. Runlevel 0 is used to halt the sys-
tem, runlevel 6 is used to reboot the system, and runlevel 1 is used to
get the system down into single user mode. Runlevel S is not really
meant to be used directly, but more for the scripts that are executed
when entering runlevel 1. For more information on this, see the man-
pages for shutdown(8) and inittab(5).
Runlevels 7-9 are also valid, though not really documented. This is
because "traditional" Unix variants donât use them. In case youâre
curious, runlevels S and s are in fact the same. Internally they are
aliases for the same runlevel.