The initial problem was there was no sound when I first started the GUI. I looked around to find the reason for this in the configuration applets provided, but found nothing that would bring the elusive sounds coming out of my headphones. At that point, I have to admit I was rather disheartened. Because Slackware was so pretty, and setup so well, I wanted it to do well in every area. The initial lack of sound meant it might not accomplish my hopeful goals for it.

Fortunately, the next reboot netted the reason why. Apparently, by default, the sound drivers for Slackware set the sound card in a muted state. Until such time as you run a command prompt level program to un-mute the sound card and save that configuration as a file, the sound card will not work properly. Once that was done, viola, I had sound. Thank the goddess for the folks who put Slackware together. They had the foresight to put blurbs and warnings into the command prompt space. I’d have given them more credit had they made the sound work right from boot one, but at least I could use their blurb to give me an idea how to proceed.

The other foible was with the mouse. While it operated for the most part, the finger wheel for scrolling flatly refused to work. Once again, I looked everywhere could in the configuration applets (which are plentiful), and couldn't find a way to make the wheel operate properly. Considering I know a bit more about computers than the average bear, I took a look at one the initialization files that make X-Windows work. There in that text file sat the answer to my problems. A little editing, and my mouse was back to working the way I prefer it to work...all the way.

Because there were some glitches, I have to give Slackware three and a half stars for device support and operability. While none of the glitches proved to be insurmountable, the fact remains that not all devices worked properly on the first boot. Had I been more careful during setup, the mouse wouldn't have proved to be problematic. A bit more explanation during the setup program would have been helpful. While it could be argued I should have known this, one has to remember I am writing this series of articles for the novice. Would this glitch have tripped up a novice? It tripped me, so I think it's safe to say a novice would have had a problem as well.

The sound card problem would have definitely been a bit more serious for the novice. Even with the blurb that showed up at the command prompt, I not so sure a novice would have been able to have successfully skirted that problem. If that person knew a bit about Linux in general, they might have made it through unscathed. If not, I can only wonder.

In my opinion, Slackware should consider making an applet that accomplishes the sound card initialization and configuration under X-Windows. Either that, or they might want to change the default operation of their sound card drivers. In any event, the fact that not all went well on the first boot leaves me with no choice but give Slackware three and a half stars for device support and operability. Fortunately, this criterion is the only low point of Slackware.

As to the fourth criterion, look and feel, Slackware gets four and a quarter stars. I can't give it five since it doesn't boot directly to the GUI. One might consider that to be a nit-picky rating. However, one of the things I stated as an ideal for operating systems tested The Linux Project is that they booted directly to the GUI. Even though getting the GUI up is simple as typing "startx" or "xinit", from the point of view of the novice, this might present a problem or at least a point of consternation. Also, by selective editing of a couple files will bring Slackware to boot to its GUI. The adventurous newbie might go there.

For myself, I kind of like the idea of having the command prompt space. It has saved my bacon a few times when I became overzealous and damaged X-Windows. It’s all a matter of what you like. If you want direct GUI operation, a little editing and some research on Slackware’s web site, and you can have it. If not, then all you have to do is type the X-Windows initiation prompt once you log in.

Once you get past the fact that Slackware doesn't boot to the GUI, and actually get GUI up and running, things change! Slackware offers numerous options at setup time for the GUI. Since there are so many different X-Windows interfaces, Slackware takes the unusual but appreciated step of allowing you the choice of which interface you want. I chose the KDE interface, and I am glad I did.

The KDE interface is nothing short of gorgeous. Looking every bit like a Bill Gates offering, the KDE interface is a sight to behold. It has the type of desktop that every computer user knows and loves. It has a start button, a system tray that holds a clock, the volume control, and a few other goodies. You also have all open programs hanging out on a very Windows like task bar. It is simply breathtaking, and completely unexpected.

Of course all that beauty comes at a price. The KDE interface is a resource hog. With this older machine, KDE has a tendency to be a bit on the ker-chunky side. However, I cannot fault the operating system for the age and speed of this machine. If it were running a newer machine, this wouldn't be a problem.

Simply put, Slackware with the KDE interface is absolutely gorgeous. If it weren't for the fact that it doesn't boot to the GUI, I'd give it all five stars. If you can handle the fact that it doesn't boot to the GUI, then Slackware is just the thing! It’s pretty, and looks just like Windows from desktop to task bar. Everything on the desktop is more or less where you’d expect to find it with your average Microsoft offering. The taskbar is a bit oversized, but highly functional.

On the fifth criterion, overall impression of the distribution, Slackware gets four stars. It wasn't completely trouble free, but given the glitches noted in the other distributions tested so far, Slackware is pretty much the most trouble free of the lot. It has its shortcomings, to be sure. However, they are fairly minor. Anyone with a bit of savvy would be able to overcome them without a lot of effort.

Upon checking Slackware's site for user forums, the minor glitches I ran into setting it up are listed, as well as the cures for them. Beyond that, there are also other hints and goodies that give you clues to switch between other X-Window interfaces and looks. While Slackware isn’t perfect, at least the folks who set it up care enough to help the user fix some of the glitches that hit you on the way. In my opinion, this is not only classy; it’s what I would expect from a group that had put together such a nice operating system. Since Slackware was also the first Linux system I ever tried long ago, I can’t help but feel that bit of gratitude they kept up the good work. It was nice then, it’s even nicer now!

It sets up relatively easily. It finds all the devices, even if you have to cajole a few of them into working properly. All the programs you get work very nicely rivaling the kind of operation we have come expect from Microsoft. The KDE X-Windows front end is nothing short of beautiful. Overall, it's what I hoped for when I began The Linux Project: an open source free operating system that is made as much for the common computer user as it is for the ultra-geek who gets off writing JAVA applets. As I said above, when The Linux Project is over, I am definitely going to set Slackware up as my alternative to Microsoft. I don't lose anything, and I actually gain a bit over the standard Microsoft offerings.

 1  |  2  |  3