Welcome to the Slackware Documentation Project

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
slackware:faq [2012/09/08 03:53 (UTC)]
nocturnal.slacker [How do I upgrade an existing Slackware Linux installation without re-installing?]
slackware:faq [2012/10/11 19:38 (UTC)]
alienbob Wrong header level
Line 37: Line 37:
  
 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? ==== 
  
-Slackware basically comes in two flavors: ​stable and current+==== What is this talk about stable and current ​versions? ====
  
-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.+Slackware basically comes in two flavors: stable ​and "​current"​.
  
-  * Stable ​is built on rock-solid componentswith well tested softwareThis recommended version will fit your desktop or server needs. +Stable ​versions are the numbered releases (1212.1, 13, 13.37 etc.). They are supported ​for a number of years after release, by way of security updatesSecurity 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.
-  * 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.+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//. 
 + 
 +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 =====
Line 69: Line 74:
  
 Read the [[slackware:​install|installation guide]]. Read the [[slackware:​install|installation guide]].
 +
 +==== During network installation I only see the "​A"​ package series ====
 +
 +You are attempting an installation of Slackware from a HTTP or FTP server. After entering the server'​s hostname and the Slackware package directory, you see the usual messages like "''​INITIALIZING PACKAGE TREE''",​ but then during the "''​PACKAGE SERIES SELECTION''",​ you can only select "''​A - BASE LINUX SYSTEM''"​. Where are all the other package series?
 +
 +You will experience this scenario when you are using a **32-bit** bootable installer image to install a **64-bit** Slackware from a webserver, or //vice versa// ((the other way round)): you attempt an installation of **32-bit** Slackware using a **64-bit** installation image.
 +
 +Solution: use the same architecture for the installer image and for the architecture of the Slackware release that you want to install from a webserver.
 +
 +==== The package installation took 3 seconds and now what? ====
 +
 +Installing more than 1000 packages should take between 10 and 45 minutes, depending on the computer you are installing them on. If the installer claims it is finished after only a few seconds, that means it did in fact not install anything at all. So what happened here? \\ This kind of issue occurs when you are not installing from the DVD or CD you booted from, but selected one of the alternative installation methods: a pre-mounted directory, or a loop-mounted ISO, //​etcetera//​. In all those cases, you have to enter a directory path to the location where the subdirectories representing the Slackware package sets can be found (the '​a',​ '​ap',​ '​d',​ ..., '​y'​ directories). \\ If you enter the wrong directory there, then the installer will not complain about your error. It will pretend that it installs packages when in fact it is not. Look at this message closely: \\ {{ :​slackware:​inshd.png |}}
  
 ==== How do I upgrade an existing Slackware Linux installation without re-installing?​ ==== ==== How do I upgrade an existing Slackware Linux installation without re-installing?​ ====
Line 109: Line 126:
 ==== 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? ====
  

In Other Languages
QR Code
QR Code slackware:faq (generated for current page)