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.
For me it depends. I always build my own kernel on older machines (I'm talking Celeron 400MHz w/ 256MB RAM, basically anything less than 1GHz and 256MB RAM) because the speed increase is noticeable. I'm sure you'd also do it if you were doing embedded devices (not that I have any experience).
Also occasionally one of the distros will ship with a particular "experimental" kernel feature disabled that I want to use.
But I would say 99% of the time I just stick with the stock kernel that comes with Debian.
Something you appear not to have considered; would you prefer to install code (kernel included) that no-one had bothered testing ???.
Using Debian stable, I'm not sure "no-one" had bothered testing it is quite accurate. But for an enterprise server, sure as shootin' you'd want to test everything in the test bed before taking it live.
I compile my own, mostly because it reduces bugginess and increases performance and teaches you something. On my system for example, there are lots of bugs if I don't disable certain things, I know I could probably disable most of them by passing options to the kernel, but that's just laziness. Also, there are things which will increase performance, sometimes drastically. And, of course, it will teach you something, especially if you've never done it before. Or you can just take the blue pill like the majority. I wonder if you know where that will get you ...
that should be generally yes for a long use system regardless if it's a new system or an old system,.. a workstation or a server.. not temporary like live systems or the likes which would be impossible or impractical