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.
I'm itching for a new slack release. My hardware really needs the 2.6 kernel to run correctly (I have an overpowered laptop and 2.6 keeps it nice and cool), and I'm urgently awaiting a native-2.6 Slackware.
I noticed the delay, too. I noticed a similar 1 week plus delay in March or April.
It'll be ready when it's ready :-)
The lack of public updates does not mean that there is no development behind the scenes. It could very well be that the changes are major enough to warrant a lot of testing and tweaking before releasing it to the public slackware-current tree. Remember that Slackware is supposed to be stable. Even -current should not have big scary bugs that kill the boxes of people willing to test the development release.
Well, I wasn't worried and I didn't think that there was nothing going on behind the scenes. I just had a feeling that there might be a release candidate brewing or something justify a freeze. Why? Because of the long gap in between updates under the current development branch. And lo and behold, what did I notice when I checked the changelog today RC status Sweet!!!