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 first problem that found during the setup configuration is that the LILO couldn't be installed automatically. Then if booting using the bootdisk fd0 (created using installation CD during setup) got the err: couldn't find kernel image vmlinuz.
I tried using the loadlin (loadlin bzimage root=/dev/hdb1 ro vga=3) and got the errors summarized somewhat like this:
VFS: cannot open root device "" or 22:01
Please append a correct "root= " boot option
Kernel panic: unable to mount root fs on 22:01
swapon: cannot open /etc/fstab No such file or directory..
the superblock couldn't be read or does not describe a correct ext2 filesyatem. If the dev is valid and it really contains an ext2 filesystem (and not ufs or something else), then the superblock is corrupt . You might try usinge 2fsckwith an alternate superblock....
I think i have to recover the corrupted superblock. I am not very familiar with this and hope all of you can help me.
since yr system is not finding the kernel image "vmlinuz" whose entry lies in /etc/lilo.conf...what i would suggest is to reinstall "lilo" in mbr using the 1st cd of the distro in rescue mode.