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.
by enloop on Fri 16th Jul 2004 14:22 UTC

My comments weren't intended to criticize Slackware. It's my impression that Patrick V. isn't especially interested in bringing Linux to the masses, so he sees little to alter his install and setup procedures.

No OS that I've used really handles the partitioning bumb well, including Windows. Windows does, however, make life simpler for the average desktop user who uses only one OS on a machine: the install procedure is biased toward devoting an entire drive to Windows. The Windows paging file and the necessay filesystems are created, of course, but without user intervention. (Experts can still play at will.) This would be a good model for desktop distributions to adopt. Offer as the default option to take over the entire drive, and build the appropriate partitions behind the scenes. Provide an expert option, of course, but don't even mention partitioning unless the user goes there.

On hardware detection: It would be nice if setup offered to show you what was detected.

I also noticed that in Slack 10 all the lines pertaining to the parallel port were commented out in rc.modules. Is that a change? I went nuts trying to get CUPS to work until i noticed that.