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.
Re: Slackmalware
by Michael Hall on Fri 16th Jul 2004 08:29 UTC

In the context of small business/community group servers:

> It has no tools to manage LVM or Raid Volumes.

Don't need them.

> It doesn't have the 3rd party support of Red Hat

Don't need it. Often too expensive.

> or a huge repository such as Mandrake's.

Don't need them. But there are Slack pkg repositories out there with more than I'll ever make use of.

> Where are the Slackware based clustering solutons?

Don't need it. Could easily build a pkg if I did need it though.

> Where are the thousands of ready to install apps?

Don't need them. Who want's thousands of apps sitting around unused on a remotely managed server with no GUI?

> what this coverage will do is turn tons of people away
> from Linux by making them think that linux is stuck
> with a 1980s installer and configuration tools.

I don't think so. The first thing anyone reading this article is going to realise is that there are plenty of Linux options with different strengths and weaknesses in different environments. For god's sake, why does one distro always have to do all things for all people, always?