Slackware 10.1
MSRP: Free
Score:
Installation
If you don't have a CD Burner, the process of gaining what you need to install Slackware can be a real chore. You have to select your floppy image, select which package sets you want, and either download a lot of data to a seperate partition or do a network install. Even if you do have a CD Burner, however, the official Slackware Mirror doesn't host a pre-made ISO image. If you don't want to make your own CD image from the files provided on the mirror, you'll have to do some Googling.
I was blessed with a CD Burner, and after about five minutes of Googling I had found the two installation CD images.
The Slackware installation program was reminiscient of a FreeBSD install, as it is a curses-like menu interface. Hard drive partitioning, package sets, and initial system configuration are all handled by this installer routine.
Configuration/System Administration
System maintanence, which includes configuration, administration, and installation/removal/updates of packages, is managed by a few core programs. The main one is pkgtool, which provides a curses-like menu where a system administrator can install/remove packages and obtain information on packages currently installed on the system.

From an administrator's standpoint, Slackware is very easy to use. It is quite stable and secure. In fact, I've been working hard trying to break it, but I just can't (short of 'rm -rf /' !) All of the packages in the stable branch have been very heavily tested, and all of the dependencies seem to place nice with eachother. I haven't run into any of the errors of dependency conflicts between two packages that seem to plague RPM-based systems (Fedora, Yoper, SuSe, etc.).
My only gripe about Slackware's package management system is the lack of an automatic package retrieval system that is the core of systems like Gentoo and Debian. There are several third-party utilities (e.g. slapt-get), but I tend to trust first-party system administration tools more than third-party add-ons.
Usage
Installation...check. System Administration...check. The only thing left was to actually, well, use it. I started gdm, and logged into XFCE, which looked beautiful, and started up Firefox and XChat. Several errors later, I realized I had forgotten my wireless card.

Being a CLI-Enthusiast, I Ctrl-Alt-F1'd back to my Virtual Terminal, and I had internet in under a minute. I went back to my X Server, and found the only bug I noticed the entire time: my X Server had a dull, gray tint to it, and there was barely any color. I tried all of the Window Managers I had installed, and upgraded the X Server with pkgtool, but the problem remained. The only way to get rid of it was to restart the X Server, so I learned very quickly to use XFCE's terminal emulator instead.
Other than the snag in the graphics, Slack was a dream to use, and every thing looked very nice.
Bottom Line
Slackware 10.1 can be summarized in two words: stable and secure. I only found one problem with Slack, albeit a major one, which was the X Server. But I'm sure this has something to do with the old laptop I was running it on.
I'd give Slackware 4/5 Penguins, and while most people wouldn't take it as a first distro for novices, I'd recommend Slackware to anybody who's used Linux before and is comfortable with the command line.
-lakerdonald