First distro I ever successfully installed and used daily - Slackware 8.

Booted to the command prompt console and was basically lost :laughing:

Fortunately, that was back in the day when Comdex was still held in Las Vegas, so I took a long lunch break and went downtown to pay a visit to the Slackware booth. The team gave me the “Linux for Noobs in 30 Minutes” tutorial and all was well after that. Had my desktop up and running with all the hardware working that night.

Learned a lot about Linux in general running a Slackware system - Fvwm was the first software I compiled from source; was my main window manager for years.

Still install Slackware now and then - usually get the unnoficial iso for Slackware current so the software stays more up to date.

have tried -

Slackware versions 8-14.2 and Slackware Current

KateOS - very early user friendly distro from Poland; well done Xfce desktop. Too bad they closed up shop.

SalixOS - solid release, good selection of packages using slapt-get

Slackel - sister project of SalixOS, based on Slackware current.

Zenwalk - Solid release, back in action after a hiatus. I think they may be Slackware Current now, too.

It’s my understanding that the next release of Slackware might be OpenRC so it will be another non-systemd option for users.


Wow, really?

I will have to try it out again if they do that, OpenRC is the best (IMO).

I tried it briefly, the lack of dependency management was lovely, it was so liberating to be able to rip out stuff I didn’t like :smiley:

Last I was reading Slackware news, that was my impression - go with OpenRC; although the changelog for Slackware Current still refers to sysvinit-scripts being built as recently as Feb. 2018.

The other issue was what to do about Wayland; they were still taking a wait and see where that project goes attitude with that.

Slackware 15 Beta available.


That’s how Slackware works. They don’t rush to new technologies/concepts/versions. They don’t change upstream code (kernel & packages). In fact, their web site is still running http, not https. Their installer has been almost the same for more than 10 years. :grinning:

1 Like

So in essence, they are slacking over at Slackware.

lol, pretty much

Not a bad thing. I would love to see AL installer stays the same for next few years. If it gets its job done better than other similar ones, no need to change it.


If it ain’t broke, don’t fix it.


:+1: Absolutely!

really wanted to learn Slack, even today. But whenever i try to i just ended up slacking…


lol, I don t even try, looks too hard ! lol

I had it backwards, which is why I wound up wearing slacks.

Downloading the latest -current ISO of the Slackware64 Beta and going to give it spin tonight.

Came across this article from Willy Sudiarto, a contributor for Slackware, regarding running Steam in Slackware without Mulitlib, nice!! Going to give this a spin and see how it performs.


How did it go? I tried their beta version in a vm. Everything went well. The new plasma DE is polished & pretty smooth.

Install was easy as usual but I did not install KDE, never been a big fan of it. I haven’t that that Steam w/o Multilib yet. To be honest, I am kinda missing AL. Pat took too long with the new release so I have totally grown to appreciate the way Arch/AL runs, feels like I am cheating on my significant other, LOL.

1 Like

Use “current” branch then. :grinning: That makes Slack rolling.

I dual boot Archlabs and Bunsenlabs that is cross pollinated with MX Linux. I am sort of polyamorous when it comes to Linux lulz.