To view parent comment, click here.
To read all comments associated with this story, please click here.
Slackware waas my first distro back at version 9.1 and it worked well at that time.
Now I use Ubuntu - something I would have rejected vehemently even a couple of years ago.
Why? Simply put..Ubuntu has progressed IMMENSELY
in two years..sure you can muck up your system with apt-get..but it that seems a lot harder to do now too and the checks against this are pretty good now.
While Slackware I would gladly use for Server , there
is just too much software that you cannot EASILY
install on slackware. And sorry .tgz files are few and far between compated to .deb packages.
Don't believe me? Try getting SCIM (an input method for asian languages) or even aMule (a popular p2p client) to work on slackware. I tried and the dependency hell was just too complex( a packaged .tgz version didnt work).
Headers? you can get all you need from Ubuntus
development repos if you want to compile something.
No need to hunt all over 
Headers? you can get all you need from Ubuntus
development repos if you want to compile something.
I've gotten into trouble with that from Debian, it's not always a simple act to know what -dev files are needed, especially if they are named differently than the binary packages they belong to. The same is probably true of Ubuntu. That having been said, Ubuntu is a pretty impressive Windows replacement, and apparently that's what most people want.
The reason why I use Linux has always been because it's free Unix, even a couple of years (kernel 0.95 and the long series of 0.99 kernels) before Windows 95 was released. That's what Slackware was meant to be, free Unix, and that's why I like it.




Member since:
2005-07-08
There is no decent package manager in Slack - Once you get used to the ease of packages you won't miss them
That works great most of the time, unless you want to install something not in the repository from source. Then you'll be chasing a thousand -dev files just so you can have the headers that Slack includes for all of its open-source programs. Then there's the RPM-hell, and even sanely packaged systems like Debian can have problems.
a standard kernel 2.4 in a modern distro is a joke - sorry to say this. And it misses out on so many features in 2.6.
2.4 is very stable, 2.6 is less-so. If you want 2.6 however Slackware offers you a choice of 2.6.17 (huge26.s) or 2.6.18 (in /testing), the latest when it was released. That's reasonably up to date. Slackware has even been "2.6 ready" since version 9.1 several years ago before it was part of the official disks. Now that it offers 2.6, why should you care if 2.4 is the default when you can change it?
where is native GNOME? It is niot acceptable that a modern Linux distribution misses out on it
Just grab it from freerock, gware, or dropline, there's nothing "non-native" about it (well, except dropline perhaps :-) ) Pat figured that since third parties were already doing a fine job of packaging GNOME, a very time-consuming process, that he didn't need to spend extra time on it that could better be used making the rest of the distro better.
It's OK that you don't like Slackware, but that's your loss. No need to whine or attack it because its not your favorite distro, especially since your complaints are easily solvable. There is however a reason why Slackware has been around so long, the reason is because in a lot of ways it's an excellent distro.