Blog post alert
Let me start off by saying: If you just want to have a working system to do your thing with minimal effort, Slackware isn’t for you (anymore).
Running Slackware today is like being gifted a Ford Model T by a weird, bearded museum curator, and then finding out that after some minor modifications and learning how to drive it, you can keep up with any modern car on the road. Only it has no ABS, AC, power steering, starter motor, crumple zones, airbags or seatbelts.
Most people who still run it (by any realistic estimate, fewer than 10000 people in the world now) have been running it since the 90’s and follow the advice not to change a running system to the letter. So why should anyone who hasn’t studied CompSci in Berkeley in the 90’s try it today?
First of all, the most widely known criticism (it has no dependency resolution) is a bit of a misunderstanding. Slackware is different. The recommended installation method is a full installation, which means you install everything in the repository up front. That way, all dependencies are already resolved. And you have a system you can use equally well on a desktop or server. It uses 20GB but disk space is essentially free now.
What if you need something that isn’t in the repo? Well, do whatever the fuck you want. Use Slackbuilds, which aren’t officially supported but endorsed by Slackware’s dev. Use Sbopkg, a helper script with dependency resolution very much like Arch’s AUR helpers. Use the repos of sister distros like SalixOS that include dependency resolution. Install RPM packages. Install Flatpaks. Unpack tarballs wherever you want them. Go the old school way of compiling from source and administering your own system yourself. Slackware doesn’t get in the way of whatever you want to do, cause there’s nothing there to get in the way.
It’s the most KISS distro that exists. It’s the most stable one, too. Any distro-specific knowledge you acquire will stay valid for decades cause the distro hardly ever changes. It’s also the closest to “Vanilla Linux” you can get. Cause there really isn’t anything there except for patched, stable upstream software and a couple of bash scripts.
Just be mindful of the fact that Slackware is different (because the Linux ecosystem as a whole has moved on from its roots).
One example:
Up-to-date Slackware documentation isn’t on Google, it’s in text files written by the guy who maintained the distro for 31 years, which come preinstalled with your system. Or on linuxquestions.org, where the same guy posts, asks for input from users, and answers questions regularly.
It’s still a competent system, if you have the time and inclination to make it work. And it’s a blast from the past, where computing was about collaborating with like-minded freaks on a personal level. And I love that.
Regular Slackware user here.
The biggest reason I use Slackware personally is that it’s the only distro I’d consider a “full system” out of the box. What that means, is that I install it, and I don’t really install much outside of the repos.
For example, the kde set comes with pretty much every KDE app. I do mean all of them. With other distros, I either have to go hunting for what packages are named what in the repos and spend hours getting everything setup and installed. While on Slackware, I pick the partitions, install, and I have a full desktop with everything I could possibly need.
Some would say “Oh, but that would take a lot of disk space.”, and funny thing about that, is with BTRFS compressio enabled. A full install of Slackware is only 4gb =P
Nice to hear from a current slackware user. Quite often these threads are populated by arch and gentoo users speculating or reminiscing about a time they used it once for a month while they were still in school.
You’ll also be probably shocked to hear that i’m a Slackware user in their 20’s =P
Been using Slackware going on 3 years now.
Not really. The only people I expect to have time to use Slackware non professionally are students.
Nostalgia. Slackware was my very first Linux distro!
Mine too! I had no idea what to do, how to do it, when where, etc… took me a good 2 days to tank my first little server :)
I think I blew up my first Slack install in about 12 minutes while trying to get a video camera to work as a webcam. It took me 3 god damned days and more than a few re-installs but I did get it going…and then spent 30 minutes web chatting with a guy from Serbia. The video was the size of a postage stamp.
I run slack with no gui as my webserver.
…been running it since 2001, guilty as charged lmao
“If you want to know how Linux works, ask a Slackware user.”
I’ve mentioned this a lot lately, but I used Slackware from the late 90s (3.x days) until about 2009 on my desktop and laptop, and about 2017 on my server. I just got tired of dealing with dependencies and switched to Debian (all three run Debian now). I had the CD subscription and would automatically receive the latest version about twice a year.
Patrick Volkerding (if my memory is accurate) has my utmost respect, and I do feel a little bad about abandoning it, but I just didn’t have the time to deal with it any more.
“If you want to know how Linux works, ask a Slackware user.”
apparently Linux works like this:
./configure
missing x
download x.tar.gzip
tar -xf x.tar.gzip
cd x
./configure
missing y
download y
... something something...
make
make install
Well, yes. That is how it works!
As someone who started with slack in '97 these modern distros function so “automagically” that I sometimes distrust them. They’ve hidden so much of the complexity of Linux and whatever Desktop Environment is running on it that most users have very little idea what’s actually happening or how it works.
That’s been GREAT for getting more people to use Linux but it’s creating the same problem that Microsoft did with Windows. The old DOS users often knew quite a lot about their PC and how it worked because they had to but as the technical barriers went down so too did the knowledge of the users. You no longer had to juggle IRQs, Memory Maps, or DLLs because Windows just did it for you.
That’s not a bash (lol) on Linux or users of modern distros either, I myself am on Linux Mint as I type this, because it was always going to work out like this. A lot of very smart people put a lot of their time into MAKING it work out like this.
I’ve used slackware more or less exclusively since the late 90s. It’s been my daily driver since I deleted my windows XP partition some time in the early 00s. It’s really all I know. Sure, I can find may way around a .deb based system when I have to. I’m also likely to apt install something, say yes to 50 dependencies, brick my system and have no idea what did it.
I love to tinker, and I love to learn. There’s no shortage of either in Slackware, and that’s why it’s not for everyone. And I don’t mean that in an “i use arch btw” way. I’m an intermediate user at best. I ask for help way more than I provide help. Lucky for me I’ve made some good friends in the Slackware community over the years.
