Slackware Linux is one of the first Linux distributions. Since the first release, Slackware has maintained and continues using simplicity, stability, and operational safety as the main features.
It does not try to rival with Windows, and it is just trying to be the best Linux possible.
Among the Slackware followers, there is a word, “when you know Slackware, you know Linux but when you know Red Hat, all you know is Red Hat.”
Slackware uses a different approach to popular distributions such as Red Hat, Debian, Gentoo, SUSE, or Mandriva Linux.
It does not intend to cover programs with fancy graphical interfaces. Instead, it puts users in total control over the system, letting them interact with it to the smallest detail.
Distribution development is not rushed to meet deadlines; each version is released when ready.
Slackware is the ideal distribution for those who like to learn and configure their own system, letting them do exactly what they want. Stability and simplicity are the reasons why many use this distribution.
Slackware Linux has the reputation of being reliable and stable, both as a workstation and especially as a server. Once installed and configured, servers can support businesses, playing any desired role, with low costs.
As with other distributions, web servers, FTP, email, DNS, and more, are functional on turnkey, as well as a wide range of desktop environments. Also included are a variety of programming tools, text editors and current libraries for those who want to compile their own programs.
Since the first release, the Slackware Linux project aimed to produce the distribution closest to UNIX (UNIX-like), trying to comply with the existing Linux standards. With the stated purpose of simplicity and stability, Slackware has become one of the most popular, stable and manageable distributions.
Another essential feature of Slackware is to include in the distribution only verified and rated packages as stable/secure (not necessarily the latest versions) and their configuration/compilation as close as possible to the author’s conception.
Slackware uses the BSD initialization scripts, while many other distributions use System V initialization scripts. In principle, on the distributions with the System V initialization scripts, each sub-directory for each run level is assigned a script sub directory while BSD distributions are assigned a script for all initialization levels.
BSD-type supporters say this is a better initialization because it’s much easier to find, read and maintain scripts. On the other side, System V scripture proponents say that using this type of initialization increases power and flexibility.
It is essential to realize that the Slackware package manager does not check for dependencies between packages. If you use Slackware for the first time, to prevent problems that may occur later, it is best to do a complete installation with all the utilities included.
Slackware officially recommends: If you have enough space on your hard drive, we encourage you to do the complete installation to get the best results.
Although Slackware does not incorporate utilities that resolve dependencies for the user by automatically downloading and installing dependencies on the Internet, some third-party utilities can provide this functionality similar to how APT does for Debian Linux.