[2024-feb-29] Sad news: Eric Layton aka Nocturnal Slacker aka vtel57 passed away on Feb 26th, shortly after hospitalization. He was one of our Wiki's most prominent admins. He will be missed.
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
slackware:faq [2012/09/01 02:51 (UTC)] – [Why does Slackware take so long to boot up?] spelling mistake corrected menues to menus vharishankar | slackware:faq [2012/10/11 19:37 (UTC)] – I can only select "A - BASE LINUX SYSTEM" alienbob | ||
---|---|---|---|
Line 20: | Line 20: | ||
==== Can I buy copies of Slackware Linux? ==== | ==== Can I buy copies of Slackware Linux? ==== | ||
- | Absolutely, just go here [[http:// | + | Absolutely, just go to the [[http:// |
==== Can I buy Slackware gear? ==== | ==== Can I buy Slackware gear? ==== | ||
- | You bet, just go here [[http:// | + | You bet, just go to the [[http:// |
==== 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 | + | Patrick Volkerding is the founder, project co-ordinator |
- | Stable versions are numbered releases (12, 12.1, 13, etc.) and are supported for a number | + | LinuxQuestions.org did an [[http:// |
- | * Stable is built on rock-solid components, with well tested software. This recommended version will fit your desktop or server needs. | + | Present contributors include |
- | * Current is the testing ground for the upcoming release. The software you will find there will often be [[wp> | + | |
- | 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 " | ||
+ | |||
+ | 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 "''/ | ||
+ | |||
+ | The " | ||
+ | |||
+ | 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> | ||
+ | |||
+ | 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' | ||
===== Installation and Support ===== | ===== Installation and Support ===== | ||
Line 59: | Line 71: | ||
This message ('' | This message ('' | ||
- | ==== How do I install Slackware? ==== | + | ==== How do I install Slackware |
Read the [[slackware: | Read the [[slackware: | ||
+ | === During network installation I only see the " | ||
+ | |||
+ | You are attempting an installation of Slackware from a HTTP or FTP server. After entering the server' | ||
+ | |||
+ | 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, // | ||
+ | |||
+ | ==== How do I upgrade an existing Slackware Linux installation without re-installing? | ||
+ | |||
+ | Read the page on [[slackware: | ||
+ | |||
+ | To track the " | ||
+ | |||
+ | 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 '' | ||
+ | <note important> | ||
==== Where do I get more information on Slackware Linux online? ==== | ==== Where do I get more information on Slackware Linux online? ==== | ||
Line 94: | Line 126: | ||
==== How do I install/ | ==== How do I install/ | ||
- | Slackware Linux comes with its own package management tools, namely '' | + | Slackware Linux comes with its own package management tools, namely '' |
==== Why doesn' | ==== Why doesn' | ||
Line 101: | Line 133: | ||
Other sources for obtaining software not found in the Slackware CD/DVD (both in source and binary form): | Other sources for obtaining software not found in the Slackware CD/DVD (both in source and binary form): | ||
- | * 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:// | + | * 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:// |
- | * http:// | + | * [[http:// |
- | * Another option is to use binary packages from http:// | + | * Another option is to use binary packages from [[http:// |
* Still another option is to convert rpm packages to Slackware packages by using the tool [[slackware: | * Still another option is to convert rpm packages to Slackware packages by using the tool [[slackware: | ||
- | * src2pkg, from http:// | + | * [[http:// |
* Last but not the least, intermediate to advanced users generally prefer to compile from upstream sources or write their own [[slackware: | * Last but not the least, intermediate to advanced users generally prefer to compile from upstream sources or write their own [[slackware: | ||
Line 114: | Line 146: | ||
* Automatic dependency handling requires constant manual developer maintenance, | * Automatic dependency handling requires constant manual developer maintenance, | ||
* 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 | + | * Several popular |
* Slackware Linux official distribution does not have the resources or manpower to manage dependency handling for third party software, which is a complex undertaking, | * Slackware Linux official distribution does not have the resources or manpower to manage dependency handling for third party software, which is a complex undertaking, | ||
- | However, there are still solutions for third-party software automatic dependency handling for those who want it. [[slackware: | + | However, there are still solutions for third-party software automatic dependency handling for those who want it. [[slackware: |
- | + | ||
- | Salix OS is a Slackware derived distribution that incorporates dependency handling. Website can be found here: http:// | + | |
+ | [[http:// | ||
==== Distro X and Y does package management with dependency handling and... ==== | ==== Distro X and Y does package management with dependency handling and... ==== | ||
Line 144: | Line 175: | ||
{{ : | {{ : | ||
Finally, select '' | Finally, select '' | ||
+ | |||
+ | Additionally, | ||
+ | |||
+ | < | ||
+ | # generated by ' | ||
+ | # | ||
+ | # Start LILO global section | ||
+ | # Append any additional kernel parameters: | ||
+ | append=" | ||
+ | boot = /dev/sda | ||
+ | compact</ | ||
Also, Slackware runs a bunch of X/GTK related scripts at startup for multiuser runlevels ('' | Also, Slackware runs a bunch of X/GTK related scripts at startup for multiuser runlevels ('' |