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.
I read couple of articles related to fsck but never got a chance to come across one.Is there any way I can corrupt my Filesystem and try troubleshooting the same?I heard that fsck shudnt be run on / and /usr directory.But say, I came across soemthing like You have corrupted filesystem and need to press Ctrl+Z to reboot after asking root password. How Can I know which Superblock is damaged?
I would add that you should not run 'fsck' on a active filesystem. You should run in 'single' user mode whenever you must repair a filesystem that may be accessed by others. The best way to ensure this is to either reboot then enter 'single' as a kernel parameter or just use your install cd/dvd to boot. That way you will be insured not to be in a multi-user environment without your filesystem(s).