|
|
|
|
|
|
by t3lp3r10n
1601 days ago
|
|
|
Surprisingly I still use Slackware (current) and actually install it on our physics department computer room using packer to generate virtual golden images and then imaging the computers with clonezilla. Slackware performs well even on those 11 years old machines that we have there (combined with some new ones). Currently students access remotely using x2go and Xfce and it works pretty well. Of course there are some problems sometimes but in general is very stable. My first Linux experience with Slackware forced me to learn how to compile the kennel to get sound... oh I had time on those years. Congratulations and thank you, Patrick! |
|
|
I've been thinking about Slackware a lot lately. Slackware manuals and the philosophy of the distro taught me how *nix, networking, and computers in general work. Back in the late '90s, that was a great contrast to the voodoo of RedHat, and frankly a humanitarian boon.
In my older enervated state, seeking something that "just works", I keep thinking of Slackware -- the only thing that "just worked" was understanding what was happening from a fairly close approximation to first principles and a software stack that did what it said on the tin. I can't think of a better distro to use in an institution of higher learning.
The irony of Slackware's affinity to the Church of the Subgenious didn't hurt either; Bob Dobbs wants to sell you a bill of goods, but once you see through all of that and achieve a state of Slack, true understanding has begun.