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.
There was an article on slashdot yesterday when the 2.6.0 kernel was released in which I noticed a lot of people pretty much saying that it's not a wise choice to use this new kernel in production environments.
The question I have is... why exactly is this a bad idea? It's already past the beta/test stages if it was deemed worthy to be an official stable release, right?
At what point do most people consider a stable kernel to be actually stable? I guess I can attribute this to the old saying, "If it's not broken, don't fix it," but that seems kind of silly considering that each kernel release is an improvement of some kind to the one before it. However, I have read about some instances where a kernel release actually broke something that worked perfectly fine in the release before (for example, something that worked in 2.4.21 that no longer works properly in 2.4.22 and 2.4.23).
The thing is, I have a few MySQL servers and I read that there were a number of changes in the new kernel that would actually improve the stability and performance of database servers. I was thinking about recompiling the new 2.6.0 kernel and using that, but if it's not stable then I'll stay away from it until, I suppose, it's "really really" stable.
Its stable, they wouldn't have released it if they hadn't been deemed unstable. But you have to realize as well, your thinking of users who used and submitted bugs to the developers, etc. In all cases, not everything is caught and you could always run into problems when using any type of software, etc.
I personally haven't upgraded yet, I see no real reason to on my servers. I am however going to upgrade my desktop to test it out first, see if its worth the upgrade, etc.