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 Michael Hall on Fri 16th Jul 2004 08:14 UTC

> 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. ;)

I've never had to do this because the security fixes have always been there when I've needed them, Slackware might be a small project but there is no slackness when it comes to providing security fixes.

Otherwise, I have built many packages from source and installed them via the standard package installer. Provided you know what you're doing (I don't accept that argument that every distro must be a complete "no-brainer", or that believing this is "elitism"), building a package is a breeze. If the byzantine complexity of making an RPM has ever baffled you, check out makepkg, the standard Slackware utility.

Documentation? Yes, well, I have to agree that it could be better ... a lot better, actually. There *is* documentation around, but no coherent, central source or repository that I know of. There's a project waiting there for someone ...