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.
It's at RC2 now according to the change log but why don't you just run current if you want the latest? I usually stick one version behind so for example when 12.2 came out, I upgraded to 12.1, I only upgraded this one on release day because it's 64 bit.
thrust me, you dont want them to rush.... one of slack's core value is stability. I dont think they would rush the dev based on people input, but if they do, we would end up only with buggy, incomplete and unstable software and thats completely opposite to slack values...
Btw, why are you so stressed to get slack 13.x? If I refer to your account info, you are using slack 12.2? Slack 12.2 was the best, IMO slack release. Thinking of 12.2 make me regret my decision to migrate to 13 mainly because of KDE4.... anyway im not going to whine about kde here, i already did on 20,000 threads all over the place ! LOL
How high do the RC's usually go? 2? 3? 100? How's it usually end up working, after a couple RC's it's usually out in a couple months? ...not in hurry or anything, just curious.
I have a suggestion. Open a tab in your browser to the Slackware page at distrowatch.com. Use that to find the release date of any of the last 4 or 5 stable releases. Open another tab and go to your favorite Slackware mirror. You'll find a bunch of directories for each release. In each directory will be a Changelog.txt. Open it. Scroll down through all the patch announcements until you find the entry date where Pat called it stable (see distrowatch). Read through the next several entries and look at the dates. That will give you an idea of what happens just prior to a release.
Sometimes it's only a week between the first RC and the stable release, like 12.2. Look at 11.0 - it went through RC5 and took six weeks. That one was excruciating for me. I bought a new laptop that needed either a new xorg or intel driver, and I needed the new Slackware to get all working. I bought the laptop in April 06, and 11.0 didn't come out until October 06 - 13 months after the last stable. But, it gave me time to try other distros to remind myself how poorly they compare to Slackware.