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.
Just annotations of little "how to's", so I know I can find how to do something I've already done when I need to do it again, in case I don't remember anymore, which is not unlikely. Hopefully they can be useful to others, but I can't guarantee that it will work, or that it won't even make things worse.
In line with the idea of reducing how much it's written on SSD, some people suggest using tmpfs for lots of things, one of them can be the ~/.cache directory. Which must be implemented in a per-user basis or with some pre-mount script that would do such tmpfs mounts before each user login. But regardless, the point is that they may spare the SSD, but not the RAM, obviously. If you quit a cache-heavy program, its cache would still be there, leaving other programs you're running with less RAM to use....
Current good quality SSDs have built-in mechanisms to level the wear on the whole device so that their lives are maximised, but for something like Swap the inherent nature of that requirement will significantly ratchet up the number of Write cycles on any drive that hosts it, and that is still something I want to avoid on my SSD.
In reality it may not be a factor, but I'd rather spend a few dollars on more RAM to reduce
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
