Nicely put there.

I found slackware and stuck with it because I wanted to learn how the linux system works. It comes with good documentation and a helpful community to support that. If a slackbuild from 14.2 doesn't build on current (many still do), then I check what ponce has, then the forums or start looking online. If that comes up null then I start figuring it out on my own because using slackware has taught me how to solve my own problems. Same deal with building packages that aren't on SBo, its easy enough to do with all development software packaged in.

3 members found this post helpful.

My thoughts exactly! Figuring out problems, particularly administrative in nature (building packages and such) is and should be the province of the sysadmin, in this case the user of the system itself. Automated package installation and maintenance in the long run has proven not to be the best in many cases (although not all; I've heard some success stories, but not so much as to convince me to go elsewhere), and knowing how to figure out problems with building your own packages has taught me a lot about how my system works. There's no better feeling than knowing that you learned something valuable when you fix a particularly vexing problem; the lesson the experience imparts tends to stick in your head more readily than one that is easily fixed.

Failure in the first,second,third...umpteenth try in fixing a problem is not something to be avoided; rather, it is to be embraced. If history has shown us anything, it is that the best success stories are inevitably preceded by many magnitudes of failures. Failures teach us more than success does. In other words, success is sweet, but it is sweeter still when it becomes the ultimate goal after many failures, than when success comes easily, and learning new things is what life is all about. The former builds character; the latter inflates an already swollen ego, and we all have known those kinds of people, unfortunately.

Happy Slacking!

2 members found this post helpful.

Hi,

The above quote is very representative of what must be done in order to allow one to resolve any issue(s). Be it trouble shooting or just diagnosing a problem. One must break problems into discernable terms that will eventually lead to potential solutions. You either know the subject thoroughly or know where to reference information that may lead you to a possible solution.

I started using Slackware with PV's first release. That was a learning curve in itself. Only my previous UNIX experience yet stepping off into the Gnu/Linux world was very exciting in knowing I would be utilizing a UNIX-like OS on my personal computer.
We as Slackware users have been fortunate to have a Maintainer and team that are dedicated to a powerful UNIX-like distribution that still has an on going development cycle. We have a Slackware-Live to allow users to test drive and promote Slackware. Plus the team maintaining a few stable releases to allow the continued use for those that may need.

Slackware on!

Hope this helps.
Have fun & enjoy Slackware!

2 members found this post helpful.

It's the end of 2021. I am using Slackware. I have started using it in 2012, and since then, I seem to have been gravitating to it. It still retains Unix-like architecture. It is basically the most Unix-like, the least MS-Windows like distro. It keeps faithful to its principle of simplicity (KISS), and it does not get bloated. It is also one of the last fortresses that does not use SystemD, which is great I am a fan of SysVinit.

Once installed it is rock-solid, and it does not get in your way of doing things. It is my favourite distro.

5 members found this post helpful.

Well-said! I've happily used Slackware since 2004, version 10.0. Slackware is very stable and secure. Over the years I've tried a lot of operating systems. Nothing comes close to the simplicity and elegance of Slackware. Slackware is my primary distro.

2 members found this post helpful.