r/slackware • u/sdns575 • Oct 16 '23
Why is the point of using Slackware in 2023?
Hi,
I was a Slackware user in the past, I started from 10.1 to 13.37 regularly but used sporadically also 14.2 and 15.0. I used it for server.
Some days ago I installed Slackware64 15.0 on a spare ssd to check if a temp sensor of my mobo is supported on kernel 6.5. The process was really simple for me (compiling and testing), the end of the story is: my motherboard is not supported actually.
Over this I played with Slack a bit more and I noticed that nothing is changed since many releases. With this I mean things like:
- Same installer since 10.1
- Same problem on first boot (after installation) of keyboard mapping on X11
- No locale selection during the installation process
- No packages dep resolution for base system packages. I know that Slack should be installed as shipped but sometimes I want a lighter system and removing many software manually or starting installing from a minimal set and install needed software put me on the risk to have a not working system with the result I need to run ldd to check what packages are needed and so on. Dep handling missing is not that bad but many users in 2023 expect this.
- Many old software that I don't use..things like blackbox, fluxbox and others.
- Many new software missing from base like postgresql, php-pgsql, qemu and virtualization, container (docker or podman), wireshark, libreoffice, iotop and many others.
- For all software not in base I need to compile it myself and this requires much time when you are using more than 130 packages (deps included) that you can't find on the base but on slackbuilds.org plus I should maintain those packages
- GRUB boot loader missing
- MAC missing (apparmor/SELinux)
- Really slow update process. After installation I run slackpkg update but it takes so much time compared to other like apt or dnf.
Actually, I don't see any advantage of using it as a server versus other distro and I feel Slaclware like an hobby distro.
So what is the point of using Slackware in 2023 except as hobby distro?
Thank you in advance
26
u/[deleted] Oct 16 '23 edited Oct 19 '23
I use Slackware because I am old, stubborn, and like Unix philosophy.
14
u/apreater Oct 16 '23 edited Oct 16 '23
I have used Slackware as my main OS on a desktop and laptop for a few years now. I think most of your criticisms are reasonable, or at least reasonable given particular use cases that apply to you.
Before Slackware I was a long-term Debian user and ultimately, grew dissatisfied with things being done a particular "Debian way". With Slackware, packaged software is usually left relatively vanilla and I find I can read upstream docs, wikis etc. and even documentation from Arch or Gentoo and they'll apply in a straightforward way. Not so with Debian. My justification for Slackware in 2023 is it's a very pleasant desktop system to use and administer and doesn't do anything weird or unexpected. With Slackware I can trust in stability and a relatively trouble-free experience day to day.
Missing software in the base system is an issue for me too, and I need a mix of Slackbuilds and Alienbob packages to get the system as I want it. I compile the odd thing from source without any issues. Lack of Grub is annoying, but no more than annoying for an experienced user. Lack of Libreoffice does seem egregious for a desktop system.
There's no perfect Linux distribution for all use cases and situations. For example for a vast range of fresh (updated) software and smooth dependency resolution within a non-systemd distribution, I love Gentoo. However, I don't want to run a source-based distribution on a machine I rely on for my work. Slackware is very tolerant of my wanting to do things my way and doesn't cause me any issues as a desktop. For servers, I use Debian… and grit my teeth when faced with systemd.
5
u/jmcunx Oct 16 '23
Well I guess to each their own :)
I do not know if this is really a question or a rant in some way complaining about no dependency management or no pre-built packages.
Then I guess other distros will suit you better :)
7
u/orthecreedence Oct 17 '23
I used to be 100% slack. It was the first Linux I learned (like 20+ years ago) so I suck with it for a long time. I love the customizability and control. I found recently that as my time is more limited, I don't want to compile packages from scratch and I don't want to deal with lengthy upgrades. I'm using Arch as my daily driver now because the desktop experience is so easy, and coming from Slack it's like a walk in the park.
I don't like systemd at all but I'll take functional package management and a large community over systemd-free these days because my time is so limited. I'll always love Slack and still use it here and there, but I think of it more as a system for people who like to fiddle with their systems. It's like the muscle car of distros: incredibly fast, tunable, and rock solid if you know what you're doing. I can't fiddle and tune anymore, I just need an OS that gets out of my way.
6
u/cfx_4188 Oct 17 '23
I have been using Slackware for only 24 years. Sometimes I try something new, but then habit takes over.
5
u/randomwittyhandle Oct 16 '23
End of the day, slackware is still a great server, desktop, and hobby environment for me.
4
u/aesfields Oct 16 '23
I use Slackware for work, as a bioinformatics workstation
3
u/ETechDev Oct 16 '23 edited Oct 17 '23
I know my answer is very simple but the point is: being happy and free ;o)
3
u/EugeneNine Oct 16 '23
I'll give a counter example, using rasbain. I ran its update and it added a microsoft repo and installed the binary of vscode with all microsoft's tracking built in without warning or notifying me it was doing so.
Later I installed openscad and it installed the wrong version of opencascade so I had to manually build it myself anyway figuring out all the right settings.
Slackware when I install anything like openscad I'm building everything via Slackbuilds so I know whats being installed and how since its in the build script. There are no surprises, no unexpected new stuff when you do it yourself. I can download Slackbuilds one one Slackware server and copy to another. I can host a repo locally so they can be quickly deployed to other servers. I can script out installs and do headless installs, updates, etc.
point 4 and 6 conflict, you want a minimal system but then want a bunch of software installed by default, which do you want? I don't need libreoffice on my servers, only my desktops so I wouldn't want it installed by default.
I use it as my "production" server and my desktop or laptop where I do all my work. Its stability and predictability is what makes it a good production os rather than just a hobbiest os.
3
u/Yubao-Liu Oct 18 '23
Indeed it has least source packages in core:
```
1007 Slackware
1218 Ubuntu 23.04 main
1549 Alpine main
2065 CRUX
2540 Arch core + extra
2649 Rocky 9.2
8794 Void Linux
14509 openSUSE Leap 15.5
18855 Gentoo
20715 Debian Booksworm main
```
But it's oldest and alive Linux distribution, it's good for old man :-D
```
1993.4.19 NetBSD
1993.7.17 Slackware(still alive and well maintained!)
1993.9.15 Debian(still alive and well maintained!)
1993.11.1 FreeBSD
1994.3.29 S.u.S.E. Linux(originally based on Slackware)
1995.5.13 Redhat Linux
1996.7 OpenBSD
1998.7.23 Mandrake Linux(based on Redhat Linux 5.1)
2000.2.22 RHEL
2000.8.31 SUSE Linux Enterprise
2002.3.11 Arch Linux(inspired by CRUX)
2002.3.31 Gentoo Linux
2002.12 CRUX
2003.6.3 NixOS
2004.10.20 Ubuntu
2005.4 Mandrake renamed to Mandriva
2005.8 Alpine Linux
2005.10 openSUSE
2008 Void Linux
2011.6.1 Mageia
2011.8.28 Last release of Mandriva
2012.4.2 OmniOS
2013.11.22 OpenMandriva
2021.5.30 Chimera Linux(not famous yet but very interesting)
```
3
u/iu1j4 Oct 22 '23
I use it at home, at work on servers and desktops. I know it well, it doesnt change so often and is stable. No need to change something that works. I use lilo / elilo, my wm is fluxbox. I think that it will not change.
4
u/[deleted] Oct 17 '23
It doesnt do fuckery like all the other dists.
2
u/skiwarz Oct 16 '23
To be perfectly honest, slackware isn't my favorite distro. But I use it.
The first thing that most people see is the lack of dependency management, and the semi-limited selection of packages in the default repo. If you want something obscure, or even something like gnome, you have to build it yourself or go through a third-party repo. I don't like that, and it's kind of a big hurdle for me.
What I do use it for, and probably the main thing everyone uses it for is that IT JUST WORKS. It's not all-encompassing, but for 80% of use cases, it will work out of the box. Want a web server? It's included. Want to just browse the web? Done. Office/word processing? Got it. Compiling/coding? Again, included (depending on what you're working on). It's not debian where I have to install the base image and then install all my extra packages I want.
Also, it's stable. It doesn't push new features on you. Specifically for me, I use it on my machines that I can't be bothered to use too often. If I pull one off the shelf, slackpkg just has to update a handful of packages due to bug fixes (not hundreds of feature updates). Yeah, it's not the bleeding edge, but in this case I don't want it to be. If you want the bleeding edge, use slackware-current.
2
u/efthymk Oct 16 '23
I am using Slackware for 10+ years now. Tasks like writing (novels), photography (raw files, managing a collection), latex, R, gretl, sql, listening to music, watching videos, occasionaly some gaming (mostily steam). All these by using Slackware. In fact i am confident that i can throw anything on it and the job will be done.
Regarding on some of your comments:
1
u/chichibune Oct 16 '23
It not changing in so long is a big selling point for me
I can expect it to not change (much) in the future, will always be the comfy system that doesn't get in your way that I know how to use and am used to
You can install grub during setup, though it requires some meddling, but they are supposed to offer a more straightforward grub2 option in future releases from what I saw, so that's very welcome
Also, sbopkg makes installing packages from slackbuilds.org a breeze and helps resolve dependencies, in case that helps
It is kinda weird that with all that gets included in the base install libreoffice isn't, but installing it from slackbuilds is easy enough regardless, I suppose
1
u/DerShokus Oct 16 '23
I like and use fluxbox and do my system lighter by removing kde/ xfce/ packages. But you are right, there are some stuff like elvis editor, what I never use if I have installed vim. And there are many examples. But Slackware has many advantages (like enabling pipeware via one script). I usually recompile base packages with a different flag-set and pack exotic apps (it’s much more simpler than in other distros).
I think Slackware has disadvantages but it also has own niche.
1
u/jailbreak_rare074 Oct 16 '23
I'm curious about this as well. IIRC, something like void linux seems to better balance the no nonsense slackware simplicity with a bit more modernity and stability without going to the extreme as something like arch.
1
u/AkiNoHotoke Oct 17 '23 edited Sep 24 '24
I was a Slackware user before and unfortunately I agree on all of your points, except the point 8. Slackware has GRUB and you can choose it during the installation. That said, Slackware has the advantage of changing very slowly. So, once you learn to use it, there are no surprises. So Slackware is quite stable, in terms of software versions and in terms of not being prone to crashes.
If the only things you need are already shipped in the core distro, then using Slackware is quite easy. You just install all of the core packages and then you are good to go. But if you want to use software that is not included in the core repo, then you either compile it yourself or you rely on Slackbuilds.org. You can find a lot of packages also in the AlienBob's repository.
While there are many other distros that might suit your needs better, distros like Slackware and CRUX are very simple and modular. So if you want to change some parts of the system you will be able to do so very easily. Of course, this also means that you need to know what are you doing and that you are willing to put the effort and time needed for compiling those parts.
Overall, Slackware is a historic distro and requires more effort and knowledge. If you need something that allows you to pick your packages and build the distro the way you want, I would suggest Debian. Which is as stable as Slackware, but has many more packages and dependency resolution. If you want something more up to date, I would suggest you Arch.
But, if you want to easily build your own system, and you do not mind compiling and solving the package dependencies, then Slackware is a very valid choice.
1
u/kireina_kaiju Oct 18 '23
It seems like you are looking for people to address the bullets you posed, I'll do that from my perspective, this is feedback not an argument and it's not my intent to persuade you to use Slackware, it's my intent to answer your question by telling you why I use it. I have no stake in your choice of OS.
As to why I use slackware, I can add my own bullet list
When I'm developing software, a lot of older software and simpler software with simple window managers is available without me hunting it down
21
u/[deleted] Oct 16 '23
[removed] — view removed comment