Thanks for a fair review. There are a couple of other resources I’d like to mention (and Pat mentions one of them in the docs included with 12.0).
First, build scripts for many additional applications are available at http://slackbuilds.org - instructions for use are also available there.
Disclaimer: I’m one of the project admins there.
Second, both Eric Hameleers and I provide numerous packages that are not shipped with a standard Slackware installation; they are unofficial and unsupported by Slackware.com, but we do support our own work. See http://slackware.com/~alien/ and http://slackware.com/~rworkman/ for details.

I think you mean, ‘Keep it simple, stupid’ principle not ‘keep it simply stupid.’

I have installed on my computer 12 distros, but mainly Im using Slackware, whats most superior over the other ones.

On my site, can be downloaded packages, inclusive actual versions of the kernel:

http://www.copaya.yi.org/tgz

@David where do you see the text “keep it simply stupid” ? in my reading i saw the text ” keep it simple stupid” maybe the author already made the correction.

for the review, it seems fairly straight-forward and without the excessive drooling i see in other reviews for other distros. i’m very comfortable using both pc linux 2007 and mint cassandra and so i doubt i will make any changes for my home use. however, in the next year, i am going to be opening my own school of english here in rio de janeiro and i wonder what i will be using for a server platform.

Good review.

I have noticed ZERO hiccups - that is, everything just seems to work

For me, this is it. The system as installed is generally very tight, stable, and quick. Some many complain about package management, but for me it has never been a problem. I build quite a bit of my own stuff, and with guys like Robbie around as well as sites like linuxpackages.net you can generally get what you need if you don’t want to do the configure-make-make install gig.

Great to have Volkerding back in good health and with a great leap into actuality. A Slackware user since 1993; but more porting and development oriented. Those build scripts are fantastic staring and imitating point. Not like redhat/fedora ramming gnome down your throat; or Suse doing likewise with KDE. Debian drives me nuts with their alphabetical ordering. Gentoo misses developers more and more with their inflexibility; and misses the desktop user also by requiring too much baby-sitting.
Slackware having brought the i486 folks into today’s linux might now go for i686 (used pentium II machines go begging). While Slackware started the classification scheme with a, ap, d, t, l, x directory trees this could be refined ‘a la’ FreeBSD ports or Gentoo portage. Big established packages (KDE, seamonkey, samba, etc) could be made optional infavor of more libraries and tools. Looking forward to many more years of great Slackware work.

Having adopted slack at v 9.0 in 2002, I’ve just enjoyed watching the distribution get better and better with every release! I botched the upgrade from 11.0 to 12.0 by cavalierly ignoring instructions, but upon realizing what a catastrophic mistake that was, then correcting it, I now happily report that i12.0 has met and exceeded my already high expectations. THIS is what the others have to measure up to, and none of them quite do it. hats off to Pat and the rest of the Slackers out there for contributing to the world’s BEST PC OS, period!

After tried many “easy-to-use desktop” distros for 6 months after years of MS, I went to Slackware from 10.0 to learn more about Linux. The slack book on my knees, I enjoy the power and ease of use of this distro. To be honnest, I actually use sabayon 64 but I do not see any difference of perf compare to Slack 11.0 though I’m going to install the 32bits Slack 12.

I have some problems with sabayon and other distros I used that never happens with Slack. I’m glad that “Pat is back” and I return back to the root of Linux.

Thank’s for your great test, just one word: for newbies who want to learn about how linux works just try Slackware.

Hello to all!

This is a fair review, indeed, congrats!

I use Slackware for desktop and servers from the 9.1 version and I was never dissapointed, this distro really works and you can relay on it no matter what.
Slackware 12 is the most cutting edge Slackware ever, but whit the same known stability and speed. It comes with the newest kernel, HAL, D-bus, Apache 2.2.4. and PHP5… even with compiz :).

The package manager tools are updated and you can easily install, remove, upgrade packages (pkgtools and slackpkg). For other slackware packages check www.linuxpackages.net and www.slacky.eu. If you don`t find there what you want, be sure that compiling from surce will work smootly. As for dependencies, you can forget about it, in allmost 5 years of usind slackware daily, I never runned into dependencies problems that cannot be solved easily. With Slackare you will never be at some company`s hand, you will be in control, and decide what is best for your setup. You will never be tight up to use THAT version of patched kernel, or that version of Apache, etc. or else you will broke something. With Slackware you will have no limitations but your knowledge, and more time you spend in slackware, more will be the knowledge.
Just try it and you will fall in love at first sight

Taking Slackware’s stability as a challenge, I installed and tried to break the thing, but everything worked. In fact, given its reputation, I’m surprised at how many different — and common — tasks I could do with it. Now I see why everyone who uses Slackware loves it: IT JUST WORKS!

There is still something important what not everybody has seen.

Slackware seems to be the only distro, whose install cd sistem includes the ext4dev and jbd2 modules, so that you can directly enter in / repair ext4 file sistems, with #mount /dev/hda1 /… -t ext4dev -o extents . Thats extremly important for people which use the ext4dev file sistem (like me using it directly, for my server)

[…] Review with snapshot […]

[…] More… […]

Way to go. Reasonable interview.
But I beg to differ.
Slackware is *great* for some newbies, those that really want to learn. Yes, we’re talking STEEP learning curve here. But everything is by the book, and you *really* have to try before you break anything in slackware. Excellent practise environment.

OK, you noticed, I’m partial to Slackware. So I’ll stop pluggiing it , and you go find out what you think yourself.

Nice review. Actually Compiz is included but I found it rather unstable.

I am a long time (since 1993) die-hard Slackware user. There are countless # of times Slackware saved me from trouble.

As for the positive about Slackware, everything installed on the system works great. The system never failed me until now (for data recovery, server type functions etc).

However, I have to give my .02 cents/euros or whatever worth of gripe regarding Slackware. This frustration I am expressing is due to the nature of my work. My work is mainly in the the security area and my primary interest is using SELinux. SELinux is very poorly supported on Slackware. PAM library integration is another area where Slackware has fallen behind. None of the newer security technologies/libraries are being integrated well into Slackware. True, it is a great server class system. It is great even as desktop system and a development system. But again, it is making itself vulnerable by loosing the security users group from using this system.

Congrats for a nice review.

I would add that for gnome people and who is not against PAM, you have also a nice desktop which soon will be ready also for slackware 12.0

Get it from http://www.droplinegnome.org

Rgds
Saxa

Solid review, though I’d be curious to hear what some of the slack veterans have to say about 12. Also, you can check out slapt-get, if automated package management is your thing. I can’t vouch for it, and everything I read suggests its a bit of a hack.

The only downside to using 2.6 as the default kernel is that now I won’t be tempted to spend 5 hours compiling a custom kernel - making it perfectly tuned to the machine, eliminating every unneeded kernel extension, cutting it to fit like a bespoke suit… Gotcha! I hate doing that!

I have used Slackware from the 9.1 version, and I have to say it is the preferred distro for me. The stability, speed and the way packages are managed it’s the best I have seen.

I agree that Slackware can be used by newbies who REALLY want to learn how to use/configure Linux. There are some good sites that will walk newbies through.

Refer to sites like this: http://shilo.is-a-geek.com/slack/
It will help a lot on the way of installing and setting up Slackware for any user

And let’s not forget that ‘Slackware’ is the coolest named distro out there

I have been using Slackware since version 1.0, as have several others who have responded here. I would like to add a few comments intended to help someone who is doing a new installation.

1. fdisk doesn’t bite people or fry hard disks. Why are people so frightened by it?

2. My favorite option for installation is “menu” which is easier to use than “expert” mode. I recommend it because it permits commonsense choices, such as
— don’t install tape drive support if you have no tape drive and no plans to install one.
— don’t install support for all the file systems under the sun if you will use only one on your hard disk and one or two more for compatibility with dos or windows partitions.
— lots of other stuff like the above.
The truly important thing is that you the user/installer have the choice in _your_ hands.

3. Every Slackware package has a brief description. Unfortunately, these descriptions cannot be read from inside the setup program. They ought to be, which I consider to be perhaps the one big shortcoming of the setup program. However, one _can_ read them during installation in order to make intelligent choices. Just do Alt-F2 or Alt-F3 to switch to virtual terminal 2 or 3 (and Alt-F1 to go back to terminal 1, where setup is running). In the other terminal you will have a command prompt. Do “df” and see where the installation CD is found. Go there, and look at the description file (same name as the package, but with suffix .txt) and read before deciding to install or not. You can read it with cat name.txt were “name” is the name of