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.
One of our linux boxes is sitting a the commnd line (bash..blah blah blah) and doesn't appear to see the kernel. Complete newbie that I am, I spent two day researching on google, ways to fix this. There were tons of command strings (None of which worked.) as well as a suggestion or 10 to try to repair the installation using the install discs or rescue disc.
Okay..so, the human who did the install no longer is employed here, having chosen to move along to so-called greener pastures and did not make any rescue discs for ANY of the umpteen bazillion linux boxes here.
My next best option was to try and repair the boot loader by starting the install and choose the option to create a new boot loader. (Once again, I point out my total noobishness.)
So, I popped the install disc in the cd rom drive (Rhel 5.1) and the system saw it, offered the option to start an install and then said there is NO RHEL disc in the drive.
Now, I know the disc is good. I works in my desktop linux box with no problem, so I thought perhaps the drive is on the fritz. I then grabbed my copy of ultimate bootCD which came up just fine, and allowed me to access the linux partitions, and view the directories on them.
This, of course verified the drives are not toast and that the cd rom may not be the problem. I then popped the linux cd back in the drive and got the same error message I got last time. I tried the disc in a different box of the sae exact make, and it worked.
Popping the ultimate boot cd back in to see if it is an intermittent problem with the drive proved only that the drive still reads the boot cd w/o problem.
This went round another 3 or four times before I gave up. The boot cd and the linux disc are from the same spindle which would rule out a firmware issue with the drive...but I admit I'm really stuck here.
Any ideas here would be most helpful and appreciated. Really...I don't have much hair left to pull out.