I refuse to read white text on black background.
Hurts my eyes.
That kind of color scheme may be fine for a game clan page where most text is on or two-liners summarizing last night's game - c001! gr8t game gang! we r0x - but not for a multi page article.

Only a matter of personal preference. I prefer white-on-black in a terminal window, a text editor or even in a word processor. Less luminosity against my eyes.

Well, then your personal preference is rather deviant.
Since VAST majority of both printed and online publications are black text on white background.

And your "less luminosity" explanation doesn't make any sence at all. How do you deal with the other 99.99% of pages that are black on white? Do you wear very dark gogles or put a dark filter over you monitor?

Maybe damaging your eye site by squinting on diminished contrast, hard to read publication is your personal preference, but I call it a health risk and find raising a complaint about it perfectly valid.

" refuse to read white text on black background.
Hurts my eyes.
That kind of color scheme may be fine for a game clan page where most text is on or two-liners summarizing last night's game - c001! gr8t game gang! we r0x - but not for a multi page article."

Can't believe your whine got you a score of 5.
it shows this site is headed to the dump.

I was wondering why he went through modifying the lines in the included xorg.conf (which seems to only be configured for VESA as a failsafe) instead of just doing "Xorg -configure" and have Xorg autogenerate an xorg.conf file with the necessary device options or use either xorgconfig or xorgsetup?

Incidentally, I was finally able to DRI working for my Radeon card with the Xorg driver using the settings for my card from this site:

I switched away from Slackware to use SuSE for a while. I switched back because my swap partitions would fill up with hundreds of megabytes and slow the system down. Not horribly, I have 3 fast drives and sometimes I configure them as a RAID 0 for speed, but still very noticeably slower.

It's not that I run lots of programs at one time that was causing all the swapping. Once the system slowed down, even with nothing but the shell running, even after shutting down X, the swap partitions were still heavily loaded until I did an init 1/init 4 or (perish the thought!!) rebooted. I attributed this to memory leaks.

Even if I was wrong about the cause, the result is that Slackware runs faster than SuSE did and that's worth the switch to me.

One of the beauties of Slackware package management is the ability to easily upgade existing Slackware packages with the #upgradepkg command which uninstalls an old package and installs the new package.
Slackware allows you to compile from source, install pre-built packages, or use SlackBuild scripts.

But I just feel at home with Slackware, setting everything like in the article at least you know it's working. I compiled latest GNOME with jhbuild and all is good, you just dont get the quirky bugs like in some distros.

Related to the groups list the article author puts the new user I found other groups were necessary o useful, namely:
disk wheel plugdev burning
without burning, for example, K3B wasn't working right. And wheel for sudo is handy.
Don't get me wrong, the articles is very good, just appeared to me this issue needed clarification.

Writing this lines from inside Swiftfox, under XFCE, running great Slackware 12... (-current really, but at this moment they are the same).

I started out in slackware around version 7. Since then I've jumped ship into various other distro's only to come to the same conclusion many do eventually. I want a distro to stay out of my way. So I'm not running Slackware again and loving it.

Slackware is perfect for me, as it lays the ground work and then lets me take it from there. I love the simplicity in it's package management, Slackbuilds are just so damn simple to create a package with. The closest thing to that for me was when I played around with ArchLinux. Both follow the KISS philosophy and don't "over-engineer" by adding layer upon layer of complexity in means to automate everything.

My only real complaint for those so called "package managers" are the over bloated dependencies that come with making packages for the masses and not on a user to user basis. Gentoo is good for that though, USE-Flags are really nice to keeping things slim and trimmed down without pulling in all these extra packages to get functionality in an application that I'm not even looking for or going to use.

Don't get me wrong, there is just a niche that Slackware fills that I fall into. I have grown over the years of using GNU/Linux to where I need this sort of flexibility and lack of hand holding.

Now to be more on topic then this generalized rambling of my own Slackware experiences, I always like seeing these kind of reviews. It was well written with some exceptions which were already corrected.