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.
Patrick V. is tentitive to switch to kernel 2.6 - in 10.0 it has to be installed manually. As long as 2.6 stays unstable, Pat can keep 2.4 the default. Then, when 2.7 DOES start (it'll just be later than usual), Slackware can switch to a then-more stable 2.6.
After all, Slack is fast enough for it to not need 2.6.
Distribution: Slackware 10.2 kernel 2.6.13, Gentoo amd64, Some mish-mash of programs that started with slack 9.0
I'm not too worried about it. I think most Slack users compile their own kernel anyway. Most of the other distros patch the kernel to add some feature not included in the base kernel and I think Linus and the gang are just trying to avoid piling on all these "extras". I've been using a self compiled 2.6 kernel since it came out and I've found it extremely stable.
Interesting quote from the interview with Andrew Morton:
"The 2.4.x core has only stabilized very recently and there remains quite a bit of tuning and mop-up work."
Very unusual bit about the distributors finishing the stabilizing of a kernel, also.
most kernel trees gain true stability, while including most of the planned features of that tree, at about patch 20-30.
And in Slackware the magic number has mostly been .1 8.1, 9.1... 10.1?
i think any considerations Patrcik V might have had in delaying or not the introduction of 10.0 had more to do with waitnig for the 2.4.27 kernel, which will finally have full support for sata drives( the last major feature to be intro'd to the 2.4 tree. I think the Slack criteria for stability will keep the 2.6 kernel 'out' as the standard kernel family for another dozen patches or so.
2.4.27 is quite close now(days/weeks?) and the 2.6 makes mostly steady progress, so I'm watching out for Slack 10.1. I do hope they clean up a few things. Frankly, since Slack 8.1 quite a few ornery 'quirks' have been steadily creeping into Slack. i called them 'bugs' one day and was immediately challenged, and really 'quirks' is a better way to describe them- little permissions problems, buggy scripts and bootdisks, and here's a cute one: You can still be fooled into thinking you need it, by reding the Slack book, and you can still click a livk to download color.gz installation disk, which has been a zero-byte file since Slack 7.0 or before. I still sometimes post to tell someone they don't need color.gz and that rawrite handle zero-byte images.
Nevertheless, Slack is the only game in town for me.