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.
No modern operating system (Windows, Linux, etc) likes to be shut down improperly which is why you should always shut it down from the start/system menu but what happens when you have multiple power outages, crashes, programs freeze up, etc over a period of weeks or months and you have no other choice but to just shut your computer off at the switch (manually)?.
In cases like this, would it be better to simply hit the "reset" button on the front of your PC or does'nt it matter?.
How do you "gracefully" recover from crashes/freezes/outages without corrupting your OS and ending up with all kinds of errors (ie; kernel panic, bad_geometry, disk error, etc) until it is so screwed up that it is no longer bootable and you have to start all over again with a complete reinstallation?.
Also, is there someway to whip your system back into shape after such crashes or some way of running an integrity check and correcting any/all problems?. I just hating having to do fresh installs every month or so.
Incidentally, I'm using Fedora Core 5 w/Gnome. Thank's for any assistance I can get on this (I really do appreciate it!).
In the case of a hard freeze you would be much better using the reset button than a hard power off as it shouldn't damage the hardware. If you have multiple freezes or kernel panics then I'd seriously look into why this is happening as in theory it shouldn't happen at all.
If you have frequent power problems then put a UPS in place, even a cheap ups with surge protection will get you over most power glitches except prolonged outages.
Fedora should check it's filesystems automatically after a crash but if you want to run a manual check then fsck is the tool you are after. Some other services may require additional checks at an application level. Databases are a good example, the tools will obviously vary on the server and backend.
Thank you. Your information was very helpful and makes a lot of sense. I will use the "reset" button from now on but will this do a better job of preventing the OS from becoming corrupt than simply using the off button?.
Also, I su'd into root and typed "fsck" and nothing happened so next, I searched for "fsck" in the package manager. Still nothing. How do I go about obtaining this tool and does it have a frontend/GUI?.