Linked by Eugenia Loli on Mon 9th May 2005 18:38 UTC, submitted by Robert Burns
Slackware, Slax "I have very mixed feelings about this release of Slackware. I do not think that the underlying philosophy of Slackware is obsolete. The concept of a system that can be configured and molded to the n'th degree is still in my opinion very much a good idea. However, this release of Slackware is not without its problems in execution." Read the review here.
Permalink for comment
To read all comments associated with this story, please click here.
Slackware is great but ....
by Anonymous on Tue 10th May 2005 23:20 UTC

Maybe I should make a wiki but for now here it goes.
Don't get me wrong, I love Slacware and have it running on all my computers (workstation, server, and a laptop).
But Slackware has more than enough faults.

First of all, Slackware as an enduser system (home computer) is a major pain.
A regular user can't do squat in default Slack install.
It's basicaly a server configuration. That maybe great for servers but it's a pain for home computers.

The permissions are such that as a regular user you can't even dial out to connect to the Internet. You can't mount drives, you can't sync your Palmpilot etc. the list goes on.
Jail like security sounds good but it's not very usefull if you can't do anything with your system other than stare at command prompt.

The installer should ask a simple question during install if it's a server or home computer install and set some sane permissions and group memberships so home users can mount their cdroms and floopies and connect to the Internet.
In this day and age where just about every home has a computer there is no reason not to do that other than PV being backward and lazy.

The purpouse fo a Linux distro should not be to teach end users the inner workings of a *nix OS but to provide a usable OS install out of the box.
I'm sure there can be a solution to provide both security and a usable system at the same time (and no, Windows is not it).

Also the installer is far from perfect. If you choose not to install Gnome from the second CD then you'll be missing libs that are needed by major apps like Gimp for example (libsrvg comes to mind) and it'll complain about it.
Those libs have to be installed later manualy.
And why the f*** does the installer insist on a domain during network configuration?! How many home computers have their own domain?

The 2.4 kernel shipped with Slack is fine for older computer s but on newer hardware you loose a lot of performance compared to the new 2.6 kernel compiled with SMP (if you have a Pentium 4 with hyperthreading) and also may not be able to boot at all if you run SATA hard drives.
HT and SATA is pretty standard on systems sold this year.

Basicaly to get a realy fast and smooth Slack install on a new system (like P4 with HT or AMD64) you have to compile your own 2.6 kernel, fix the broken udev, blacklist a bunch of "stuff" in hotplug and only then you have a modern, fast, very responsive, and stable OS install.

I think the reason Slackware users are so loyal and devoted to Slackware is because once they go through the initial tortures and very painfull configuration of Slack install they are terified and scared shitless that they would have to go through the same ordeal if they switched to another distro.
Slackware is like the mob, once you're in you're in for life, there is no way out :>(
And if someone says Ubuntu is the "witness protection program" for Slackers, you know how it goes, you can run but you can't hide, Slackware will find you anywhere (and then you'll get your rc.S in the back of your head when you least expect it) :<o)