SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Since I have already recompile a 220.127.116.11 kernel for my 10.0 version it would be safe to say I would go for the 2.6 when I get 11.0 version.I rarely compile a kernel and usually stick with the vanilla version. It might be a bite bloated, but I haven't seen a real increase in performance from the kernel I have recompiled.
Most of the servers I run are at home, so they aren't really that important, but even for a production server I would still keep the original kernels, just for the fact that if a server every did go down because of hardware failure, and you have to migrate it to a new server. There is better chance of being compatible with the new server, this could certainly save some headaches in the future.
Distribution: Slackware each x86 + ARM and Porteus
I use 2.6.13 since 10.2 all the time in 3+ serves, laptop and homePC
so it stays 2.6 in 11.0 (already installed)
I customize only: low-latency preemptible 250Hz and nosmp...
I leave it i486 and pached with bootsplash (for slackware advertising purposes)... ;-)
I'm long since on 2.6 (since 2.6.0) and i like it for speed, low latency and stability.
I don't thik 2.4 is realy worth to stay in at least 85% of cases: IMHO I would call it outdated rather than confident:
5. various new drivers and patches...
6. it's linux for crying out loud, if we don't test it they won't ever fix it.