Why Slackware Still Matters
An anonymous reader writes "In a rebuttal to the recent opinion column "Does Slackware still matter?" at Linux Watch, cRaig Forrester provides insight into Why Slackware DOES still matter--and not just to "hard-core group of hobbyists" or "highly professional" Linux server administrators--but desktop users and newcomers too."
I don't think most people would agree with the following: "So, does Slackware matter? Simply put, YES. Slackware matters because Slackware IS Linux." The reality is that many people who are experimenting with Linux for the first time now use Fedora or Ubuntu.
I will say this though. I definitely harbor fond memories of using Slackware from 1995. I remember vividly those Boot and Root 1.44MB floppies and trying to install from their extremely early packaging system. Ah the memories...
--
Free 411! 1-800-411-SAVE
Free Conference Call -- No Spam, High Quality
Throw me in the "newcomer" camp.
As it happens I just installed Slackware on an old PC I had lying around. Though I had installed and used other distributions before my experience with them was quite limited and I've been mostly a Windows user.
I chose Slackware merely because it was the easiest to acquire. They offer the torrents right from the official website and they're always well-seeded. I got both CD's in what seemed like no time at all.
After about a week of usage, it's been holding up fairly well, even with the ancient specs my old PC has. It was even able to support a wireless adapter I stuck in there after I installed madwifi. However I definitely needed a lot of outside help in accomplishing that task, and overall though I was able to get it installed and running fine, a total newbie would have gotten nowhere. If Slackware wants to appeal to that demographic at all (which it very well may not) it needs to fix that.
audioLibre - freedom of music
Ubuntu froze during the disk partitioning program on my PIII 700MHz, 64MB Thinkpad. SuSE spelled it right out, "You have too little memory to run the installation program, please activate a swap partition." (Sure, if you would just let me run fdisk!) Slackware installs and runs without a hitch. Slack matters to me.
I totally agree with you. I've always been wary of RPMs, probably due to the same ignorance that people claim that slackware either doesn't have or has inferior package management. There have been situations where my RPM database said that an RPM wasn't installed but it was, and I didn't have the patience to sort it out. Also, the RPM dependencies insistence, only defeatable with --nodeps (which maybe caused my RPM db issue) always interferes with a project. Slackware now has slapt, although one can easily do an upgradepkg ./* from a directory of packages. The dropline and freerock management systems make keeping your windowing system up to date a breeze.
And most importantly, Slackware has actually prompted me to _understand_ what all the bits are for. I have an edge now, because I never started with magical RPMs or a magical up2date (although those tools are available now in various carnations for both RPM and tgz packages). I still recommend slackware to people who want to learn about linux.
It's also considered a conservative distribution, which tends to mean it will stay with a stable version for longer before upgrading. That's official though. You can always compile your own from source and then CREATE a package.
There are great home-made packages available from www.linux-packages.net and various other sites.
I love slackware, and hope Pat's healthy and having a good time.
Yeah!
"When the solution is simple, God is answering." -- Albert Einstein