r/slackware • • Dec 26 '16

Slackware future

Hi, is slackware still a distro worth investing time into? I do like the concept and the stability but should i go down the path or should i rather take a look at gentoo? I am fairly capable with linux so i guess i would like to take one step further. Thanks!

4 Upvotes

26 comments sorted by

7

u/[deleted] Dec 26 '16

We get a little tired of questions like this.

Try it out, dude. Find out for yourself. Those of us who use it rely on it every day, so yes, I'd say it's worth your time.

2

u/mokarbroj Dec 26 '16

Would you mind sharing your use case?

2

u/[deleted] Dec 26 '16 edited Dec 26 '16

I rely on it as my primary workstation. I mostly have worked as a DevOps engineer and Operations support technician for cloud and hybrid computing. It tends to be my portal into machines I administrate, which are mostly going to be amazon linux, ubuntu, rhel, and centos.

I also use it for development. I've mostly worked with ruby in the form of chef cookbooks as well as cloudformation templates. I use it heavily for docker research and development, and I also use it heavily for building out networks of virtual machines for testing.

I do a little bit of gaming on it too, from time to time.

It's really the only Linux distribution I'm comfortable working on as a workstation. As I've mentioned elsewhere, I would not recommend it for servers, there's just too much work that needs to be done to make it as friendly in server-space as other distributions out there that already dominate that market.

1

u/mokarbroj Dec 26 '16

Hey, thanks for the info. I'll try dig myself more into it.

5

u/[deleted] Dec 26 '16

Slack will not waste your time with distro-isms, useless complexity, broken software and constant changes.

Thanks to the very long (eternal, almost) updates lifecycle, it also has a place in the server space, at least for small companies and personal projects, where there is no imposition of 'enterprisey' systems.

RHEL/CentOS should be your absolute main focus if you want to do sysadmin work.

Gentoo I've always seen as a hobbyst time sink with no application for real professional use.

4

u/[deleted] Jan 02 '17

I like Slackware because:

  1. Its not rolling release, and it is up-to-date with security, you can easily install newer versions of software if required via slackbuilds, so this is ideal for desktop and servers.

  2. There are no pointless configuration scripts what make distros even more complicated especially if things go wrong. You get to learn how everything works properly, so that means you can solve problems easy. I'd say Slackware is one of the easiest distros to use because of that.

  3. Every release of Slackware pretty much stays the same just with updated versions of the software. Although they did stick in Pulse Audio in last release but only because Bluetooth depends on it, otherwise I'm sure they wouldn't of bothered, however its dead simple to remove pulse audio.

  4. They don't include pointless complicated stuff like systemd, selinux, pam, etc. Maybe Slackware is the only distro left what doesn't use them?

  5. Slackware is a purist linux distro what proves you don't need any other crap on top of it, and thats what makes it special :-)

3

u/[deleted] Dec 26 '16

Gentoo and Slackware are both highly capable and popular distributions. Which one you choose is up to you but I don't think you're going to be "wasting" anything regardless which one you choose.

2

u/dermusikman Dec 27 '16

Slackware is as close to "pure Linux" as you can get, really. Like sethbrown had, I'd experimented with other distros for a long time and always came back to Slackware. If you understand how Linux and the GNU tools work, you understand how Slackware works. No bullshit. No fluff. It's stable, reliable, and your fault if you break it.

That said, I like to experiment. I did eventually find a new home in Arch Linux, which has been my primary desktop distro for a long time. It carries a lot of the Slackware philosophy, but with a solid, modern package manager and bleeding-edge list of packages. It is more likely to break but, again, I have complete control of the system with great documentation and little "magic" to blind me.

So, I'd recommend that if you have a reasonably stable set of needs, Slackware is an ideal distribution. If you expect to experiment with new packages and suites, Arch Linux may better suit that need.

There's something to be said that I still subscribe to the Slackware subreddit after having not used it a long time... it'll be my fallback indefinitely.

2

u/livestradamus Dec 28 '16

-All the hottest babes love a slacker. -Has a totally bad-ass name. -Lots of Linux cred with big gray beards. Everything else has been mentioned above.

2

u/dogcatchersito Jan 17 '17

I just wanted to chime in a little. I Do IT work but most places that I have been never run linux. So to get away from some of the issues that happens day to day on windows machines I would use Linux. I had Mint for a while and netrunner but got tired of the forced updates. As well as the new version of the Distro that I was using. I performed a Distro update once and that was the end of that distro immediately switched to Slackware and started to learn. After that everything else seems a little easier but I don't get unwanted distro updates. I am using it for college on a Ultra light. and the only challenge now is the student login to use the wireless. most times I can get a work around to work but others I flat out fail. All in all I love working with it and wouldn't give up that little nugget of not being pestered to update my Distro.

1

u/ezzep Jan 06 '17

Slack and gentoo are of two different schools of thought. Slack give you the options and tools to tweak linux to your heart's desire. You don't have to tweak anything though. Do what you want. Gentoo....you get to tweak it because you are kinda forced to almost. I like slack more because I learned how to use commands and Google. And I don't have to run emerge package and wait 5 years for things to install.

On the other hand, I loved suse linux before they changed to opensuse. I remember when zypper first came into production. It hosed YAST and then it hosed the updater app. It turned suse into bloat city. Now things are some better. I still hate zypper.

-4

u/mayhewrich Dec 26 '16

A difficult question.

I would say that Slackware should not be taken seriously. Just enjoy it but if you need an 'investment' look elsewhere. However it makes great production servers, laptop and desktop installations. It depends on what are your objectives.

4

u/[deleted] Dec 26 '16 edited Dec 26 '16

Ya know...

Slackware has been the only solid workstation I can rely on for years at this point, I'd say it should be taken seriously... as a workstation.

I actually would very much not recommend it for servers, especially not production servers. As we move towards more and more cloud and hybrid (cloud/dedicated hybrids) computing, slackware just doesn't fit that niche. The majority of tooling available just doesn't work with slackware... yet.

I keep meaning to do something about that, but it's a lot of work for one person, and I've got a lot of other work to do.

I treat Slackware as a porfessional workstation only, and that's how I recommend it to people interested in trying it.

2

u/mayhewrich Dec 26 '16

Perhaps I am not acquainted with Cloud computing as you are, but I am hosting a Nextcloud server on my Slackware server and I am very satisfied.

5

u/[deleted] Dec 26 '16 edited Dec 28 '16

My big issue with it is that it's not well suited to utilize tools out there that provide automation. Or, rather, the way slackware does things is not targeted by a great deal of tools.

When you have slackware servers, the tendency is going to be to treat them like pets. This works fine in a dedicated environment, but cloud computing, at least production-level, value-add-to-a-business type cloud computing, should be done with a "cattle vs pets" mentality.

Every machine needs to be disposable and replace-able. We should be able to delete machines automatically and not have to worry about it.

Slackware can do this, but there are common automation tools that might get tripped up on the init system, in particular. You'd also need to rely exclusively on bash scripting to automate package management.

There are also some slackbuild packages that cover one issue that makes slack less cloud friendly, but you really need to dedicate yourself a build server if you want to take advantage of them.

I'll give the mysql-utilities slackbuild as the obvious example. With that I can install the mysql client tools without also having to install the server, which you would normally have to do using official packages, but, if you aren't using a build server, you still need at least a handful of development packages installed on your machine to build it. You might find you need to write custom slackbuild scripts to accomplish this for some tools, increasing developer time spent just setting up the operating environment.

While you can certainly dedicate a build server to doing this work so that you can deploy minimal slackware web frontends, as an example, you still have the burden of maintaining a build server, as well as maintaining and automating the build process.

There's just so much work you have to do, as the sysadmin, to conform to cloud computing best practices if you choose slackware to actually deploy a product. It can definitely be done, but it adds unnecessary operational overhead to any deployment.

3

u/lightbulbjim Dec 26 '16

Yep, Slackware makes a great pet but poor cattle.

2

u/[deleted] Dec 26 '16

Thoughtful and well-reasoned points. Thank you for sharing.

0

u/[deleted] Dec 26 '16

[deleted]

4

u/[deleted] Dec 27 '16

This is a brilliant way of describing Slackware.

0

u/mokarbroj Dec 26 '16

Don't get me wrong i do find slackware quite interesting. My concern is regarding its future and dev. Since you've been a user for 10 years would you recommend someone this distro, regardless of its fair dev team. Maybe i should have said that i would like to get more into it im my free time, not fulltime production. Can this distro be used as a daily driver and server

2

u/mayhewrich Dec 26 '16

Is there life after Pat?

Who knows?

I was led to believe that there is a contigency plan but I am not optimistic because egos would get in the way. Perhaps a fork might replace it seamlessly but then it would not be Slackware anymore.

This a good reason to enjoy Slackware while it lasts.

1

u/jmcunx Jan 02 '17

I would not worry about this, I remember reading somewhere many years ago when when PV took sick there was a plan in place.

2

u/WaytoomanyUIDs Jan 27 '17 edited Jan 27 '17

From what I recall it was actually a bit confused at first, then the Brazilian Slackware community quickly stepped up to provide patches for a while, and then IIRC Eric Hameleers, Robby Workman and some others took over, basically the same guys who help develop Slackware these days. There is an official policy in place now if something similar happens

0

u/[deleted] Dec 26 '16

[deleted]

1

u/mokarbroj Dec 26 '16

Thanks for the overwhelming reply! I will take a look at those suggestions, they sound very interesting. Again thank you for the info i have a clearer picture now and i will go the slackware way. Have a great new year!

1

u/garpu Feb 07 '17

Actually, I thought there was a plan of succession, should the BDFL become incapacitated? I seem to recall there being made mention of it when he was sick a long time ago.