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.
The installation goes over fine, and then it gets to 'Installing Boot Manager' and that's going fine until it hit's creating initrd, because it jump's to 62% and stay's there. I know that the kernal takes awhile to install but I left this over night, to see if it would just take a long time, but I doubt it would take 8 hours to install kernal. So any ideas?
Sorry. This is the entire story:
Some problems with install cd's may arise from corrupted files downloaded from the internet. To make sure the iso file you donwloaded is ok, there is a tool called md5sum. Md5sum is an algorithm that writes a string of characters which are unequivocally associated with each file. If you run a md5 program against your file and then you compare your string with the one provided by the site from where you downloaded the file, and both are identical, the file is ok.
To use this, you must have a md5 program and the string provided by the site. Most mirrors and ftp's do provide md5sum's of all their files.
If you have a win computer, you should install a md5sum program. If it is a lin one, the md5sum is already installed.
Hey friend, I forgot to mention, the md5 issue is not the only possible reason why you have those problems. I thought it would be worth saying, because md5 check is the first thing we do on iso files, as they are so important for a system being well installed. Corrupted files can give errors in an unpredictable way.
But if you say there are other linuxes that also can't be installed, I'm no longer sure its a md5 issue....