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! I have experienced inodes and ext filesystem corruption for quite a long time already. But since I recently installed a linux system on an old desktop. I realize the importance of filesystem corruption as a more important issue (before was just a nas machine, so I didn't care that much).
The slackware checks the disk whenever it is mounted 32 times (/dev/sda1). The last time I mounted, I saw a 0.9% contagious error on startup. Since I knew the e2fsck command, so I just repaired the disk, clearing the inodes. I have researched online that inodes are to do with the permission and path of the files in the filesystem. I am not sure if it is actually safe to just clear this information. What could I do if I experience this problem in the future?
I also realized that the NTFS and FAT disks don't have the same problem. I am sure that windows based filesystems have an analogous to this. But why doesn't a windows desktop prompt the same error?