| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision |
| slackware:faq [2012/09/08 03:53 (UTC)] – [How do I upgrade an existing Slackware Linux installation without re-installing?] nocturnal.slacker | slackware:faq [2012/09/25 05:07 (UTC)] – [How do I install/upgrade/remove software in Slackware Linux?] updated internal link mfillpot |
|---|
| |
| Present contributors include [[wiki:user:alienbob|Eric Hameleers]] (aka AlienBOB), Robby Workman (aka rworkman), Stuart Winter (aka MoZes), Eric Jan Tromp (aka alphageek), Alan Hicks, Mark Post, Fred Emmott, Vincent Batts, Heinz Wiesinger (aka pprkut) and several more. | Present contributors include [[wiki:user:alienbob|Eric Hameleers]] (aka AlienBOB), Robby Workman (aka rworkman), Stuart Winter (aka MoZes), Eric Jan Tromp (aka alphageek), Alan Hicks, Mark Post, Fred Emmott, Vincent Batts, Heinz Wiesinger (aka pprkut) and several more. |
| ==== What are the different versions? ==== | ==== What is this talk about stable and current versions? ==== |
| |
| Slackware basically comes in two flavors: stable and current. | Slackware basically comes in two flavors: stable and "current". |
| |
| Stable versions are numbered releases (12, 12.1, 13, etc.) and are supported for a number of years after release, by way of security updates. The "current" branch is a "rolling" system with relatively frequent and potentially disruptive updates to the system. New users and users looking for a stable system for production use should //always// use a (fairly recent) stable release. | Stable versions are the numbered releases (12, 12.1, 13, 13.37 etc.). They are supported for a number of years after release, by way of security updates. Security updates are added to the the "''/patches/packages/''" subdirectory of a Slackware release tree on every public mirror. Functional updates are not added to past releases. |
| |
| * Stable is built on rock-solid components, with well tested software. This recommended version will fit your desktop or server needs. | The "current" branch on the other hand, is a //development tree// which is always split-off from a recently released stable Slackware directory tree. Usually this split-off happens some weeks after the stable release. \\ It marks the start of a new development cycle towards the next stable release. At the end of a development cycle, a Slackware release is created by renaming the top-level "//slackware-current//" directory to "//slackware-NEWVERSION//". Slackware-current is known to cause relatively frequent and potentially disruptive updates to the system. New users and users looking for a stable system for production use should //always// use a (fairly recent) stable release. The Slackware developers assume that anyone running slackware-current realizes that he/she is in essence, //a beta tester//. |
| * Current is the testing ground for the upcoming release. The software you will find there will often be [[wp>Upstream_%28software_development%29|upstream]]'s latest version. For more information on current, please visit the [[slackware:current|dedicated page]]. | |
| |
| If you want to know when the next version will be released (at time of writing the most recent stable release is 13.37), it will be ready... when it will be ready! There are no fixed release dates, as the Slackware goal is to deliver the most stable Linux experience. | To sum it up: |
| | |
| | * //Stable// is built on rock-solid components, with well tested software. This recommended version will fit your desktop or server needs. |
| | * //Current// is the testing ground for the upcoming release. The software you will find there will often be [[wp>Upstream_%28software_development%29|upstream]]'s latest version. For more information on current, please visit the [[slackware:current|dedicated page]]. |
| | |
| | If you want to know when the next version will be released (at time of writing the most recent stable release is 13.37), it will be ready... when it's ready! There are no fixed release dates, as the Slackware goal is to deliver the most stable Linux experience. |
| |
| ===== Installation and Support ===== | ===== Installation and Support ===== |
| ==== How do I install/upgrade/remove software in Slackware Linux? ==== | ==== How do I install/upgrade/remove software in Slackware Linux? ==== |
| |
| Slackware Linux comes with its own package management tools, namely ''pkgtool'', ''installpkg'', ''upgradepkg'' and ''removepkg'' for installing, upgrading and removing software packages. ''makepkg'' can be used to create packages. See also [[slackware:slackpkg]] and the page on [[howtos:how_to_use_slackware_installing_software|installing software]]. | Slackware Linux comes with its own package management tools, namely ''pkgtool'', ''installpkg'', ''upgradepkg'' and ''removepkg'' for installing, upgrading and removing software packages. ''makepkg'' can be used to create packages. See also [[slackware:slackpkg]] and the page on [[howtos:slackware_admin:how_to_use_slackware_installing_software|installing software]]. |
| ==== Why doesn't Slackware Linux have my favourite "XYZ" software included in the CD/DVD? ==== | ==== Why doesn't Slackware Linux have my favourite "XYZ" software included in the CD/DVD? ==== |
| |
