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.
every time when i boot up my computer my fedora core 2 hangs at audit ( some crazy numbers) initialized for more than 5 mins is this normal or it's just me ? is there a possible way to reduce the waiting time ?
Originally posted by qwijibow I use fedora core 2.
on my Athlon 1333mhz 512 meg ram 6gig hard disk, fedora core 2 boots in just under 40 seconds....
But i do boot a custom compiled kernel, and i made a custom run-level (4)
on a default install it booted in about 1 minute.
No, its not normal to take that long.
What is the message on screen when it hangs ?
What is the output of 'dmesg'
what hardware on you running on ?
1) it doesnt give me any error messages, it just hangs there for 5 mins, than go on to the next steps, it's pretty strange
2) i am running on a amd 3200 xp, 1gb double channel ddr memory. gforce 5900 fx
i think i hardware are fast enough to handle the system, it got be something else.
i have a raid card inside my machine could this be the problem ?
thank you for your quick reply
well, as matter of facts I have 2 raid cards, 1 is silcon image, the other is built in by Asus, the chipest is Nvidia
and i htink, you are right, i should go to their website and do some research there,
Well, nash ist starting and then the systen hangs.
It *can* indicate that there is something hanging in the initrd (initial RAM disk). As already said, it *can* but it does not
necessary mean that.
nash is a small, yet powerfull, let's call it "shell" for executing the linuxrc script in the initial ram disk.
After nash, INIT is executed, but in order to do this the root filesystem needs to be mounted.
So there is maybe a problem in mounting the root filesystem (e.g. root device hangs, etc.)
Therefore we need more information about what'a actually going on during boot. So we need to increase the
level of verbosity during boot.
If you are using the GRUB Loader, take a look on the file /boot/grub/grub.conf .
If there you can find "quit" as boot parameter, then delete it and save the grub.conf file. This will increase the level of verbosity during
the boot process.
If you are using LILO then take a look on the lilo.conf file. Since I use GRUB I suggest that you take a look on the lilo.conf
manpage for parameter settings. I *think* that you have to enter verbose=5 in the global section of lilo.conf, but consult
man lilo.conf to be 100% sure.
I would also suggest that you take a look on your initrd image.
The initrd Image is located in your /boot directory and is named like initrd-2.x.y.img, where 2.x.y is the kernel level.
Copy this image to a different directory, e.g. /tmp
cp /boot/initrd-2.x.y.img /tmp
Do not forget to replace x and y according to your kernel level e.g.: initrd-2.6.7-rc2.img
change into the destination directory and decompress the initrd image
gunzip -S .img initrd-2.x.y.img
This will produce a uncompressed image (now without .img extension in the file name) of the initial ram disk, which then can be mounted as loop device
Create a temporary mount point for initrd and mount the decompressed image:
mount /tmp/initrd-2.x.y /tmp/initrd-mnt -o loop
(Remark: gunzip produced an uncompressed image of the original file,
that does not have the .img extension in the file name)
Change now into the initrd mount-point
In the subdirectory ./lib (/tmp/initrd-mnt/lib) you can find the modules being loaded at stratup
linuxrc (/tmp/initrd-mnt/linuxrc) is the script executed by nash.
Take a look at it
If you find there some commands that appear to be strange, they are all listed in the nash manpage