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.
Hi, starting this in a new thread to try and get a bit more help - I mucked something up while trying to sort out another problem discussed in the 'Seeing'my windows partition thread
Okey dokey - Here's the details of my new problem ... how do I get out of this one? The following is transcribed from where it all started to go wrong during the boot!
WARNING: bad format on line 2 of /etc/fstab
fsck ext3: EL = /boot:
The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternative superblock:
e2fsck -b8193 <device>
/home: clean, 269068/10944512 files, 4027182/21870481 blocks
No such file or directory while trying to open EL = /boot
*** An error occured during the file system check
*** Dropping you to a shell; the system will reboot
*** when you leave they shell
Give root password for maintenance (or type Control-D to continue)
After typing in the root password I get the line
(repair filesystem) 1 #
Absolutely no idea what to type after that ....