Linked by Michael Hall on Thu 15th Jul 2004 07:35 UTC
Slackware, Slax My first experience with Slackware Linux came with version 9.1, after 4 years of using various versions of Red Hat and SUSE Linux. I disliked the general direction these distributions were moving in and didn't see their increasing focus on the "big end of town" as auguring well for either myself or clients of my small one-person IT consultancy business. I quickly became a Slackware convert and have since used it exclusively for all my server deployments. Check in for more and 15 screenshots from Slackware 10.
Permalink for comment
To read all comments associated with this story, please click here.
docs and updating slack
by johnMG on Fri 16th Jul 2004 05:40 UTC

When I first tried Slack, I was disappointed that the docs on the official Slackware site seemed incomplete and a bit out of date.

Although I'm not currently now a Slacker, I think a point to remember about Slackware is that -- thanks to its simplicity -- it exposes the deficiencies (or strengths) in the underlying components of the system. That is to say, if software package X has lousy docs and a complex config file, then that's just what the maintainers of program X have provided. If you don't like it, consider contributing to the efforts of the good folks who work on developing program X.

That's important because it puts the responsibility of a quality user interface on the actual folks who are developing the software. This is good for the community, as it makes software better for all of us.

Debian worked *great* for me in the past (as a desktop), until something went wrong -- then I was up the creek with a very difficult-to-figure-out paddle. I'm sorry, it was a long time ago, and I can't recall exactly what problems I had with it, but I recall that fixing it involved using some of the more esoteric features of the dpkg or apt tools. At that point, you begin to wonder, "maybe it would be easier if I just learned how to install and config the software by-hand myself?"

I suppose this is different in a large enterprise setting.

A question about Slackware: when you've got version n.3 of some piece of software installed, and version n.3.1 is released (say it's a security fix), what's the standard and smooth way of upgrading while still keeping your old configuration? (Assuming the fix *just* came out, so there's no binary package available yet, and you don't want to wait. ;)