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.
You must log in or register to comment.
So you’re saying it’s essentially BSD but wastes more of my time. Got it.
I mean, I think it started as a BSD fork with a Linux kernel jammed in so… you’re not far off.
Is my summary here correct?
- slackware installs all software in its repos by default.
- there’s no package management or dependency resolution. If you want to delete something, or install something, you do that on your own
No. It has a package manager that installs, removes and upgrades packages.
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
kdeset 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
Damn, squeezing all of that down to 4gb is impressive!
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.
I’m not a student, I got a full time job =P
I stand corrected.
KDE was an example, but a lot of other things come out of the box with Slackware. And of course, that package isn’t a thing that comes out of the box.
You using slapt-get for updates?
Only for 3rd party repos, but for main updates, I use
slackpkgsince it automatically prompts me for updating configs and all that.
Ngl i would try running the popular distros or a distro based on the popular distro
I’ll always have fond memories of it. I learned a lot back in the day and swore by it.
I’ve been using various GNU/Linux distro over the course of the last 20 years. When I started out, packages could never be too fresh and cutting edge. Nowadays I’m an admin and I administer way too many VMs. I dream of a system that I never need to update. While I know that’s almost impossible if you want to be secure now might finally be the time I give slackware a try. I’m also old enough to be more curious about learning less but more in depth.
I run slack with no gui as my webserver.
…been running it since 2001, guilty as charged lmao
I don’t think you answered the question on the title. Why should most people not use Slackware?
Praise “Bob!” For we have Slack…ware! I actually haven’t tried it yet because I’m a new user running fedora and Slackware still seems above my paygrade, but as an avowed SubGenius and linux user, it is my destiny to try. I have an old laptop to try it whenever it will bring me Slack, I’m saving this thread for information purposes, thank you. PRA’BOB
Not all distros need to appeal to the mainstream. Diversity is a good thing in and of itself. In biology, it makes ecologies more robust, and there’s no reason it shouldn’t do the same for a software ecology.
The day when there’s no longer a place in Linux for Slackware, Gentoo, LFS, Alpine, and other independent non-mainstream distros is the day I move to BSD.
Nice write up, and there’s lots of choice so although Slackware was the first distro I ever ran, back in the 90s, it probably still has a place.
I’m interested in your take on security, without updates. Do you consider Slackware is secure?
Slackware gets security updates backported to its package versions, like Debian. If you run Slackware Current, it’s actually just as active as Arch or Debian Sid. But for the software you install from outside of the repo, keeping it updated and secure is on you. I just use Flatpaks cause I’m a lazy Slacker.
Thanks, I was wondering how that worked.
Why would Slackware be insecure? The only trust is in the package manager, which comes with checksums and a maintainer who has a good track record
Vulnerabilities found in packages? The maintainers aren’t omniscient.
That’s good Slackware, don’t you waste that Slackware.
When they dropped reiser the lug broke up mostly along Debian or gentoo lines. It was hard to switch to Debian. You just can’t freely disconnect and connect things like in Slackware. You can’t just rpm2tgz some package and see if it works.
You can’t top the level of troubleshooting knowledge gained from using that distro.
About the only thing a Slackware user can’t tell you is how the system got installed. He just hit enter a bunch of times.
“This is actually the same as the menu option”
Umm so why are there two options?
Legacy Support for old Automation Scripts (Script expecting to press
erather thanm)¯\_(ツ)_/¯
If you hate bloat you like Slackware. It doesn’t assume anything about how you want to use your computer, so it’s more painful for a lot of folks. Other distros will try to do things for you and will ultimately end up doing something someone doesn’t want. With Slackware you learn a lot and you get a rock-solid system that will do whatever you like, but you have to be willing to manage it.
But I thought slackware installs the entire repo by default. Is that not very much bloat?
Every Linux user should try Slackware at some point.
I did Linux From Scratch once. I got it to the point it was booting a kennel that supported everything I needed, had a working init (sysv), a helper script that “installed” packages (symlinked stuff to integrate them into the system) and kept “recipes” for whatever I compiled.
If I had kept going and compiled everything I needed and kept maintaining that I’m guessing it would have been pretty close to the Slackware experience, right?
It was very cool to know I can do all that and I learned a lot but if I had kept going I feel like it would have become limiting rather than empowering.
Like, it’s cool to go camping and catch your food, and cook it, and sleep outdoors and to know you can survive in the wild, but I wouldn’t want to have to do that every day.
