Enjoy Slackware 15.0!

Welcome to the Slackware Documentation Project

Trace:

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/01 03:10 (UTC)]
vharishankar [How do I upgrade an existing Slackware Linux installation without re-installing?] added a phrase 		slackware:faq [2012/10/11 19:38 (UTC)]
alienbob Wrong header level
Line 20: Line 20:
 ==== Can I buy copies of Slackware Linux? ==== ==== Can I buy copies of Slackware Linux? ====
  
-Absolutely, just go here [[http://store.slackware.com/cgi-bin/store]]+Absolutely, just go to the [[http://store.slackware.com/cgi-bin/store|Slackware Store]].
  
 ==== Can I buy Slackware gear? ==== ==== Can I buy Slackware gear? ====
  
-You bet, just go here [[http://store.slackware.com/cgi-bin/store]]+You bet, just go to the [[http://store.slackware.com/cgi-bin/store|Slackware Store]].
  
 ==== Why spend money if I can download Slackware Linux for free? ==== ==== Why spend money if I can download Slackware Linux for free? ====
Line 30: Line 30:
 Indeed, Slackware Linux will forever be freely available for download, no strings attached. However, consider:\\ Slackware Linux is developed by Patrick Volkerding as a full-time job. The sale of Slackware Linux CD's, DVD's and paraphernalia is his only source of income. The core team of developers working with Patrick do not get paid, but should Patrick have to stop developing Slackware because he can no longer support himself enough to do so, the distribution will then have a very uncertain future. Indeed, Slackware Linux will forever be freely available for download, no strings attached. However, consider:\\ Slackware Linux is developed by Patrick Volkerding as a full-time job. The sale of Slackware Linux CD's, DVD's and paraphernalia is his only source of income. The core team of developers working with Patrick do not get paid, but should Patrick have to stop developing Slackware because he can no longer support himself enough to do so, the distribution will then have a very uncertain future.
  
-==== What are the different versions? ====+==== Who are the people behind Slackware Linux? ====
  
-Slackware basically comes in two flavors: stable and current. +Patrick Volkerding is the founder, project co-ordinator and chief maintainer of Slackware Linux. He is also known as BDFL (Benevolent Dictator for Life). Several active contributors also help Patrick maintain the distribution. 
  
-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.+LinuxQuestions.org did an [[http://www.linuxquestions.org/questions/interviews-28/interview-with-patrick-volkerding-of-slackware-949029/|interview with Patrick Volkerding]] recently. That interview covers a lot of ground, including mentions of past and present contributors, their involvement, and a brief history of Slackware Linux. 
  
-  * Stable is built on rock-solid components, with well tested software. This recommended version will fit your desktop or server needs. +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.
-  * 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.+==== What is this talk about stable and current versions? ==== 
 + 
 +Slackware basically comes in two flavors: stable and "current". 
 + 
 +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. 
 + 
 +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 62: 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 70: Line 94:
  
 If you wish to perform a major upgrade from an earlier release to the latest stable version, you should read and follow the instructions in ''UPGRADE.TXT'' and ''CHANGES_AND_HINTS.TXT'' files provided in the official Slackware CD/DVD or internet mirror for the appropriate version (that is, the latest version). If you wish to perform a major upgrade from an earlier release to the latest stable version, you should read and follow the instructions in ''UPGRADE.TXT'' and ''CHANGES_AND_HINTS.TXT'' files provided in the official Slackware CD/DVD or internet mirror for the appropriate version (that is, the latest version).
-<note important>Before upgrading the system, it is recommended that you always take a complete backup of your data.</note>+<note important>Before upgrading the system, it is recommended that you always make a complete backup of your data.</note>
 ==== Where do I get more information on Slackware Linux online? ==== ==== Where do I get more information on Slackware Linux online? ====
  
Line 102: 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? ====
  
Line 109: Line 133:
 Other sources for obtaining software not found in the Slackware CD/DVD (both in source and binary form):  <note warning>Note that the licensing of some software may only permit redistribution in source form. Please do not redistribute or make available online any binary packages of software you compile from source unless you are sure the license permits it. Also avoid packaging and redistributing proprietary software without the creator's permission.</note> Other sources for obtaining software not found in the Slackware CD/DVD (both in source and binary form):  <note warning>Note that the licensing of some software may only permit redistribution in source form. Please do not redistribute or make available online any binary packages of software you compile from source unless you are sure the license permits it. Also avoid packaging and redistributing proprietary software without the creator's permission.</note>
  
-  * There are quite a few trusted and well-respected individual Slackware contributors who make their SlackBuild scripts and binary packages available online. One source is http://slackware.com/~alien/ and another is http://rlworkman.net/pkgs/ +  * There are quite a few trusted and well-respected individual Slackware contributors who make their SlackBuild scripts and binary packages available online. One source is [[http://slackware.com/~alien/|AlienBOB's repository]] and another is [[http://rlworkman.net/pkgs/|Robby Workman's packages]]. 
-  * http://www.slackbuilds.org/ is a community source of high quality and tested build scripts that make it easy to install third-party software on Slackware, and sbopkg, from http://www.sbopkg.org, makes processing SlackBuilds easier.  +  * [[http://www.slackbuilds.org/|SlackBuilds.org]] is a community source of high quality and tested build scripts that make it easy to install third-party software on Slackware, and [[http://www.sbopkg.org|sbopkg]], makes processing SlackBuilds easier.  
-  * Another option is to use binary packages from http://slacky.eu or other binary Slackware package sources. Note that packages are contributed by the community and the quality of packaging may vary from person to person. +  * Another option is to use binary packages from [[http://slacky.eu|Slacky.eu]] or other binary Slackware package sources. Note that packages are contributed by the community and the quality of packaging may vary from person to person. 
   * Still another option is to convert rpm packages to Slackware packages by using the tool [[slackware:rpm2tgz|rpm2tgz]].    * Still another option is to convert rpm packages to Slackware packages by using the tool [[slackware:rpm2tgz|rpm2tgz]]. 
-  * src2pkg, from http://distro.ibiblio.org/amigolinux/download/src2pkg/, can be used to build packages from source, and to convert other package formats (.deb, .rpm) to Slackware packages. The [[http://software.jaos.org/#cpan2tgz|cpan2tgz]] program is able to build Perl modules into packages.+  * [[http://distro.ibiblio.org/amigolinux/download/src2pkg/|src2pkg]] can be used to build packages from source, and to convert other package formats (.deb, .rpm) to Slackware packages. The [[http://software.jaos.org/#cpan2tgz|cpan2tgz]] program is able to build Perl modules into packages.
   * Last but not the least, intermediate to advanced users generally prefer to compile from upstream sources or write their own [[slackware:SlackBuild_scripts|SlackBuild scripts]].   * Last but not the least, intermediate to advanced users generally prefer to compile from upstream sources or write their own [[slackware:SlackBuild_scripts|SlackBuild scripts]].
  
Line 122: Line 146:
   * Automatic dependency handling requires constant manual developer maintenance, and adds potential for dependency hell.   * Automatic dependency handling requires constant manual developer maintenance, and adds potential for dependency hell.
   * The official Slackware Linux distribution is anyway meant to act as a cohesive whole. Hence, dependency management is largely moot as installing the entire distribution (the recommended way) takes care of most dependency problems.   * The official Slackware Linux distribution is anyway meant to act as a cohesive whole. Hence, dependency management is largely moot as installing the entire distribution (the recommended way) takes care of most dependency problems.
-  * A significant number of Open Source software can be compiled with different dependencies based on compile-time configuration switches. This makes dependency handling harder and more error-prone for binary redistribution of third party software.   +  * Several popular Open Source applications can be compiled with different dependencies based on compile-time configuration switches. This makes dependency handling harder and more error-prone for binary redistribution of third party software.   
   * Slackware Linux official distribution does not have the resources or manpower to manage dependency handling for third party software, which is a complex undertaking, requiring a lot of testing and is prone to errors as already noted above.   * Slackware Linux official distribution does not have the resources or manpower to manage dependency handling for third party software, which is a complex undertaking, requiring a lot of testing and is prone to errors as already noted above.
  
-However, there are still solutions for third-party software automatic dependency handling for those who want it. [[slackware:slapt-get|slapt-get]] is a package manager that adds dependency handling for third party package sources like http://www.linuxpackages.net and http://www.slacky.eu.  +However, there are still solutions for third-party software automatic dependency handling for those who want it. [[slackware:slapt-get|slapt-get]] is a package manager that adds dependency handling for third party package sources like [[http://www.linuxpackages.net|LinuxPackages.net]] and [[http://www.slacky.eu|Slacky.eu]]. 
- +
-Salix OS is a Slackware derived distribution that incorporates dependency handling. Website can be found here: http://www.salixos.org/+
  
 +[[http://www.salixos.org/|Salix OS]] is a Slackware derived distribution that incorporates dependency handling.
 ==== Distro X and Y does package management with dependency handling and... ==== ==== Distro X and Y does package management with dependency handling and... ====
  
Line 152: Line 175:
 {{ :slackware:servises-2.png?nolink |}} {{ :slackware:servises-2.png?nolink |}}
 Finally, select ''Exit'' end press ''Enter''. Finally, select ''Exit'' end press ''Enter''.
 +
 +Additionally, if you use LILO, Slackware's default boot loader, you can add the ''compact'' option to ''/etc/lilo.conf'' to speed up the boot process by merging read requests from adjacent sectors:
 +
 +<code># LILO configuration file
 +# generated by 'liloconfig'
 +#
 +# Start LILO global section
 +# Append any additional kernel parameters:
 +append=" vt.default_utf8=1"
 +boot = /dev/sda
 +compact</code>
  
 Also, Slackware runs a bunch of X/GTK related scripts at startup for multiuser runlevels (''fc-cache'', ''update-mime-database'', ''gtk-update-icon-cache'', ''update-gtk-immodules'', ''update-gdk-pixbuf-loaders'' , ''update-pango-querymodules'' etc.). These may be disabled manually by commenting out those lines which refer to them in the file ''/etc/rc.M'' but don't disable anything unless you're absolutely sure you know what you are doing! These scripts are essential for GTK applications to render fonts and icons properly. Also, Slackware runs a bunch of X/GTK related scripts at startup for multiuser runlevels (''fc-cache'', ''update-mime-database'', ''gtk-update-icon-cache'', ''update-gtk-immodules'', ''update-gdk-pixbuf-loaders'' , ''update-pango-querymodules'' etc.). These may be disabled manually by commenting out those lines which refer to them in the file ''/etc/rc.M'' but don't disable anything unless you're absolutely sure you know what you are doing! These scripts are essential for GTK applications to render fonts and icons properly.

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