I have just installed the latest version on my desktop machine (which isn't a state-of-the-art machine by any means.) Had to install wicd from the extra directory to get my wireless network going but everything else is working fine. It looks good, it works, it don't patronise you like other distros, I love it.

Here's a way to have a PC fully powered. Even an old one. No bad surprise. No bulls**t. Good reactivity of updates. No 140 cd's set you'll never use.
I like the poor graphisms during installation because they introduce no bug.
The configuration tools (net, packages...) are quick.
On the Slackware site, you have The Book, from which you can learn Linux really fast.
The packages system is strong. No dependencies headaches.
A LOT of packages at http://slackbuilds.org/

Slack leads you from newbie to expert :
I've learned more slackin' 6 monthes than 10 years of others OS (including other Linuxes).
Well, please stop reading and just go for it.

P.S.: Big thanx to Patrick Volkerding and all other people who makes Slackware.

Back on the years 00's, I was introduced to Linux by one of those old magazines, on which there was a Mandrake install cd. I installed it, and didn't thought much of it. A while later, while talking with a friend, he introduced me to Slackware, and the Slackware KISS philosophy, and how things "just worked". I would reinstall the system multiple times just for the sakes of it, configure the ALSA drivers, make the damn WinModem work, and have mplayer play the first Matrix directly from the shell.
It was a fun time, and it was an awesome introduction to that phenomenal distro that Slackware is. It is incredible to see how much things evolved, how many apps we have out of the box, and how much stable Slackware still is. Whenever I needed something done, there was for sure a way to do it and it would STAY THAT WAY forever.
I still use only Slackware today, and it is the only Distro I would recommend to anyone. All those other distros with dependency manager and wanna-be Windows alternatives with cute dialogs and "press this button that I'll configure and lock down everything for you", they might work for an end-user that doesn't care much about Linux and that just wants an alternative to Windows. But lets be honest, they can't even get close to the "user-friendlieness" that Windows has, so they don't really fulfill they purpose. Slackware however, has the intent of being stable at the same time as it is COMPLETE and highly configurable. And it accomplishes this goal magnificently, better then any other OS.

At $47.90 (including shipping) for a two-sided DVD (64-bit version on one side, 32-bit version on the other), Slackware 13.37 is a steal. Of course either (or both) versions are available free to a good home from any number of sources; e.g., LinuxQuestion.org http://iso.linuxquestions.org/slackware/, Oregon State University Open Source Lab http://ftp.osuosl.org/pub/slackware/, but I prefer to support Slackware development in what is really a small way by paying for the jewel case and its content.

Installation is a breeze -- insert the media, reboot, wait a little while for the CD-ROM/DVD to load, log in as root and you're ready to get on with it.

If it's a new machine, the first thing you would want to do is partition your disk drive (at least a root and swap partition) using cfdisk /dev/sda (for a SATA drive) or, if it's an already-in-use system, you don't need to partition anything unless you want to change it for some reason.

Next you execute setup and you're presented with a few questions to answer (assign drive partitions, automatic or manual installation [so you can pick in choose if you don't want "everything" installed]); the basics. I always do a full, automatic install -- in these days of 500 G to terabyte disk drives, there really isn't much reason to pick and choose unless you're interested in stripping things down to the bare essentials.

One common complaint about the installer is that it's not gooey; frankly, that's what I really like about it. It's text, it's simple (and thus elegant) and you don't have to wait forever for the thing to figure out what you've got in the way of hardware so you can click-'n'-drool your way through what is pretty basic stuff.

On the four machines I maintain installation takes no more than 15 minutes start-to-finish. That includes setting the root password and network configuration (typing addresses and the like). It usually takes me another 10-15 minutes to "fine-tune" the things I want a certain way -- setting up printers and plotter with HPLIP and CUPS, setting up NTPD, getting web pages and HTTPD running and the like. I also keep a few add-on packages from SlackBuilds.org http://slackbuilds.org/ and I'll install the packages from those (or, if GLIBC has changed, rebuild the packages and install them).

So, it's up, it's running, now what? How is Slackware to actually use?

Frankly, it's a dream machine -- it stays out of my way and it comes with everything already installed. Well, it doesn't come with OpenOffice.org/LibreOffice.org, but those are freely available from SlackBuilds.org and it's a quick (well, not that quick; they're roughly 18 M) download-and-install using the built-in Slackware package management tools.

Also, I've never been able to wrap my head around BASH. I've been a Korn Shell user for some decades and I'd rather fight than switch -- Korn Shell is included with Slackware, no fiddling around downloading it from somewhere or other then struggling with getting it installed and changing the default shell (I simply edit /etc/passwd -- carefully!).

I am a heavy user of a console; I've been at this on and off for... oh, dang, about 50 years (starting in 1961 with punch cards) and I'm perfectly comfortable with typing the name of a utility, some options and hitting the carriage return. A lot of folks aren't comfortable with that and prefer the "click-'n'-drool" school of computer use; I ain't one of them. I'll use a GUI-based utility if it makes life easier (K3b is one that truly makes life easier burning a CD-ROM or DVD!), but, generally, I'll type it if I can before going off and finding a different way.

Two of the best things about Slackware are:

• It is the most un-fooled-around-with distribution there is; there is no "branding" in KDE, Firefox, Thunderbird and other utilities. What you get is what the developer(s) intended.
• It is the most like System V. If, like me, you bounce back and forth between Slackware and, say, Solaris, well, you appreciate that. A lot.

My machine are, typically, up and running for months without a reboot.

I think that pretty much says it.

No matter how many distros I try I always end up back with Slackware; the first Linux I ever tried (Slackware 9).

I have it running on desktop and 2 laptops and it just works and works great!

It allowed me to use Linux, especially the way he is exposed to download. I used dial-up to download ".isos",use dial-up task is arduous. But by the way that exposes your files is Slackware much easier. Now no longer use dial-up I use adsl, but I got used to Slackware.

On at least one lap top, I needed to switch to the 2.6.38.4 Kernel because the graphics was more clunky with Pat's preferred Kernel.

Slackware really suits my needs. I can install, configure and uninstall any programs without breaking others.

Running Slackware is boring - because nothing breaks.<br>

This is good. I was ending up in a heap with an rpm based distro every 2 years, and worked with someone who was rinning cad and pcb software for 8 years on the same box with slackware. What slackware does, it does well. ATI video works well in 13.37 - no small juggling feat that. Ditto, I am sure nvidia.

Once you are not afraid of hacking a config file, and know what you want, you can do it with slackware - painlessly. Some distros package the sun java plugin, at least one packages an alternative (blackdown?), slackware packages non iirc because anybody can and should grab one. /Etc/acpi scripts ditto - I have seen 50 scripts (.csh & .sh varieties) from some distros, of which 48 are useless. you get a defsult.sh with slackware; if you want 50 scripts, it supplies an editor, and expects you to use that. Noobs can flounder here. But that editor is called directly. I have seen /usr/bin/vim as a symlink to /etc/alternatives/vi which is a symlink to /usr/bin/vim-iMproved :-//.

I have grown to like the slackpkg. From viewing it as a disadvantage, I now see it as a painless plus. It's so easy to make your own, which makes compilations less intrusive, because you can delete exactly what you installed. I never run a make install any more.

My pet hate is KDE - that monstrous piece of bloatware that makes windows vista at it's worst look fast. I have yet to see kde on a box it didn't slow to a crawl. I think I have seen a program load in under 5 seconds in kde, but that's the exception.

VERDICT: Great if you're not a noob.

I like slackware, using it since long long time ago, version 3.2, My server still running with 12.2, there is no need to upgrade it after doing slackpkg upgrade. slackware still support it.&lt;br&gt;13.37 is my first 64bit version on my desktop, really nice to see it running smoothly.&lt;br&gt;

Been through a few distros over ten years. From Mandrake to Elive to Ubuntu, but Slackware seems the cleanest, started with 13.1.

Slackware is a great tool for learning Linux. The 64 bit version of 13.37 is great for running 64bit VM's. You can have your 32bit apps running with Multilib support, so you get the best of both worlds!

You can choose to compile your own software, however Slackbuilds.org does an excellent job of providing install scripts for a wide range of packages.

No dependency support for software? Most Slackbuild scripts list the dependencies so you can install them. Create a queue in order of dependencies and you are on your way. It's not that hard!

I don't use KDE as a desktop, so couldn't comment on the quality of it with Slackware, Xfce suits me fine at the moment.

Slackware can be quite addictive, I enjoy it anyway, give it a try!

I gave a 9 because I think never will exist a software that deserves a 10 (nothing is perfect).

What I love about this distribution is the stability, I know there are another distributions highly stable but this one, damn! I love to come at home and spend my time using the computer and not fixing it.

If you know what you are doing it's pretty easy to configure and maintain, and if you don't know you have many documentation to do the things in the right way.

The only bad thing is that you may need to compile some applications, small ones aren't a problem but big ones can be, anyway always you can find builds from another people so really it isn't a big problem either, just can be a little annoying for newcomers or people that doesn't like to compile their own software.

For me Slackware is, by far, the best Linux distribution ever!!

I think my hardware had it's first orgasm the moment I logged in for the first time on Slackware 13.37!

I seriously love Slackware for it's simplicity, reliability, stability and ease of use.

I use it as a desktop system, and It has everything i need right out of the box (except flash player), plus a zillion things I might need at some point in time. All I had to do was create a user, set up a basic firewall and tcp wrappers, install flash player and voila! Java is already there so I can access my bank right away. Python is there so I can waste some time when there's nothing on TV. I installed KDE, but I use XFCE, and KDE programs are available in the XFCE menu. The slacker life is good.