Post by Eli the Bearded
However, I wouldn't recommend it for production use. It is still
maintained primarily by a single person whose age and health have
negatively impacted the project. It does not reliably receive timely
Is it true that it is not really recommended for production work?
Sounds about right. Here's a test you can do if you have an AWS account.
Select "Public Images". The region I'm looking at has just over 100k
(109,706). Try a search.
ubuntu -> 31,958
debian -> 21,095
centos -> 3,399
Post by Eli the Bearded
slackware -> 0
That's pretty strong evidence that people don't use Slack for cloud
computing, and if it isn't used for cloud computing, it isn't used for
I have one more important thing to consider when choosing distribution
for a production environment and that is how long into the future your
choosen version of your choosen distribution is going to be supported.
Yes, Slackware might partly mostly be a one man show and there is no
guarantee that the current stable version of Slackware is going to be
supported X years from now. However, in practice, Slackware does support
its old releases for longer than most other distributions do. At the time
of this writing Slakcware 14.0 which was released 2012 is still
supported, the last security patch was
dnsmasq-2.85-x86_64-1_slack14.0.txz released less than a week ago. So a
Slackware release made almost nine years ago is still supported.
Lets compare compare with the top 3 production environments on AWS:
Ubuntu: Its LTS release 16.04 reaches EOL about now, in 2021-04. 16.04
was released 2016, the same year that the current stable release
Slackware 14.2 was released.
Debian: Version 7.0 was EOL 2018, 7.0 was released 2013, the same year
that still maintained Slackware 14.1 was released. Since then also
version 8.0 relased 2015 has became EOL 2020.
CentOS: Version 7, released 2014, is said to get maintenance updates
until 2024-06-30. Version 8 released 2019 will not get any updates after
the end of 2021. Since CentOS has become a rolling release "beta version"
of RedHat I would not consider it for production. Also, I would not use
Slackware-current or any other rolling release distribution for
I must say that it was mostly by coincidene that I started with Slackware
in the mid 90s as a complement to Sun workstations. The choice then was
between Yggdrasil and Slackware and somehow Slackware felt more future
proof. During the years I have gotten many good advices to switch
distribution, in chronological order those pieces of advice came about in
* Switch to RedHat because its package management makes it easier to
* Switch to Debian because its wide range of supported software
* Switch to Mandrake bacause it is the way of the future
* Switch to SuSE because it is part of United Linux
* Switch to Ubuntu because it is easy to install
* Switch to RedHat because you can pay for support
* Switch to CentOS because you don't have to pay for support
During all these years I have never regretted sticking with Slackware.
Many others have listened to the advices and found themselves with
distributions that suddenly cost support money per installation, get
During all these year Slackware has simply kept on rocking the same way,
the only suggested distribution that would come close to that is Debian.