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.
SlackwareŽ 13.37: <<<< Release Candidate 1 (rc1) >>>>
What's this 13.37 business? Look at 'Leet' to get scoop.
If you are running 13.1, first read the text files for '-current' to note changes or hints that may relate to your system
To download -current, create DVD ISO use Alien_Bob's-script -mirror-slackware-current.sh Be sure to note your architecture by changing parameters or passing parameters to script. Script is well documented. Slackpkg usage:
Be sure your version is 13.1 . If not then perform upgrades as suggested by each 'upgrade.txt' for your version level(s) to 13.1.
You can use slackpkg by first selecting a mirror in '/etc/slackpkg/mirrors' then run 'slackpkg update', 'slackpkg install-new', 'slackpkg upgrade-all', 'slackpkg clean-system'.
Until Slackware 13.37 is stable you will need to either create your ISO via Alien_Bob's script above or use slackpkg to update your 13.1. You should read all the available text documents;
Keep in mind that you will not be able to find a release tree stamped with "13.37-rc1" or such. The "13.37-rc1" number is just a reflection of the state of the slackware-current (i.e. the development) tree.
For the young padawans among us, the procedure goes as follows: at some point in time, a copy is made of the "slackware-current" directory and that new copy will be renamed to "slackware-13.37". Official ISO images will be created for that version of Slackware, it will be pressed onto official DVD and CDROM sets, and these will be available for purchase at the Slackware Store (http://store.slackware.com/).
After a little while (Pat and team take a break first) you will see that the slackware-current directory will start receiving updates again. Also, somewhere before or after that first movement in slackware-current, there will likely be critical bugfixes to slackware-13.37 (and previous official releases). Those updates are going to be added to the "patches" directory you will find in every online Slackware release tree.
Note that stable releases will only get their severe bugs fixed with no new features getting added anymore, while the "-current" tree is always in an evolving state (towards the next stable release).
This decision was probably based (my opinion, not Pat's) on the post on http://planet.mozilla.org/ where the following snippet of agenda was posted:
Schedule & Progress on Upcoming Releases
Firefox 4 (Desktop)
* RC1 looks like it will be the final build, so far no showstoppers found
o several issues have been identified as potential ridealongs, meaning we might do a 4.0.1 release
o continuing to do triage daily
* assuming RC1 holds, the planned ship date is March 22nd at or around 7am PDT
* reminder to QA + press that unadvertized MU from 3.5->4.0 and 3.6->4.0 will be available on release day
(i.e. users will be able to do Help -> Check for Updates to see an update to 4.0)
If Slackware 13.37 ships well after 22 march then you'd have a good chance to see an official 4.0 final included.
It is time to push this into the main tree. It's unlikely that we'll see
significant changes prior to Firefox 4.0 final. Probably the first security
fixes for the Firefox 4.0 branch will come with Firefox 4.0.1, which is the
branch that we'll want to be tracking in Slackware 13.37's /patches. If for
some reason you want to stick with Firefox 3.6.x, it will be tracked in
Slackware 13.1's /patches for as long as they support it upstream.
Sun Mar 27 08:28:47 UTC 2011
There have been quite a few changes so we will have one more release
candidate: Slackware 13.37 RC 3.14159265358979323846264338327950288419716.
Very close now! But we'll likely hold out for 126.96.36.199.
Well there you have it. The answer you all have been looking for, all that time! ;-)
The list of changes is again pretty long. It shows that “declaring a Release Candidate” has a good reason. People ask from time to time, why these release candidates? Thy are nothing similar to what the bigger distros use in their progression towards a stable release. Things like “feature freeze” and “show stopper bugs” are used in Slackware development too, but you won’t see those mentioned in the ChangeLog. They are not relating one-to-one to any of the Release Candidates. Instead, the first call of a Slackware Release Candidate causes many people to try and install Slackware-current for the first time in a development cycle. Not many people are anxious to use a development release, especially since all of us keep repeating “when you are running -current, we expect that you know what you are doing, and that you are able to fix a suddenly broken system by yourself (with the help of the community)“. The Release Candidates are a sign of stability for those people. And we need all of you to help with the final stage of development! All these new people testing the pre-release result in many bugs found and forgotten features requested, and this causes a surge in the stabilization process which makes Slackware the rock solid distro we all know.
Last edited by onebuck; 03-27-2011 at 05:05 PM.
Reason: Add Aliien+Bob' release canditate comment
What? Not from here, they're not.
The first points to a thread started by rmjohnso in the Slackware forum.
The second points to a thread started by alan_ri in the Non-*NIX forum.
The third points to a thread started by rajatmendus in the Non-*NIX forum.