Okay, I'm getting REALLY tired of having to dig through the documentation for things that should be obvious. Keep in mind that it's been a couple of days already - I've just condensed it for your reading pleasure. Maybe all the Gentoo users rave about the documentation more than other Linux users because they HAVE to use it. Also, I'm really starting to feel that I'm learning Gentoo, not Linux, and that Gentoo is really getting in my way. My frown is growing.
To make a long story short, I got KDE running under Gentoo. I did have to let it run all night to compile, though. But no sound, no wireless, no ACPI, no battery monitor, nothing. At this point, all I had was a Linux kernel with X.org and KDE running on it, and I was thankful for the network interface. I got the mouse buttons fixed by switching from "IMPS/2" to "PS/2," though this was more random chance than anything else. I had to CTRL-ALT-BKSPC a few times to kill X and get to my terminal window, run VI, and pray again.
Oh, Slackware, wherefore art thou?
In trying to get everything else working, between digging through wrong Gentoo doc after wrong Gentoo doc, tons of links I dug up on Google, and reading through man pages, I really started to feel even more like I was learning Gentoo, not Linux. Many Gentoo skills were not exportable to other Linuxes. And I had only met 1 of my 3 goals (nVidia drivers installed, and wouldn'tcha know it, Gentoo has a custom install - why? The .RUN file is SO EASY!). That little voice wouldn't stop pestering me... so, after three days of struggling, endless compilations that took forever, endless digging through manuals online, hardware that just wouldn't work, and probably other gripes, I pulled Slack 10.2 off of Bittorrent, set the seed to indefinite, uncapped a fresh Dew, and burned myself a couple of discs.
In 40 minutes, I was staring at KDE in Slack 10.2 (compared with 3 days in Gentoo), my sound worked, the tray had the nifty battery monitor, the nVidia drivers were installed and working, I never had mouse problems, and all I had left to do was tackle the wireless driver, which took some time but wasn't impossible; my Linksys WRT54GX needed a firmware upgrade which, after the upgrade, resolved all wireless issues. I'd like to give a shout-out to James Ketrenos, the ipw2100 driver maintainer, for all his help. This is half of why I use Linux (the other half is doing what I choose with the computer I paid for!).
I've said it before and I'll say it again - Slackware "just works." Really. I use slapt-get because I like Jason's responsiveness and the community support, but I find that my "source-based" distro, unlike Gentoo, takes hardly no time at all to "./configure; make; make install" applications that I need. Additionally, I don't have to mess with USE parameters and countless other Gentoo "optimizations." Again, allow me to don the flame-resistant suit: if you like Gentoo, for better or for worse, then I'm HAPPY FOR YOU. I just couldn't stand to learn Gentoo when what I want is to use Linux.
With Slackware, the only "weird" thing is the BSD-style startup scripts, which are just "weird" because they're not used as much as the SysV startup scripts. But Slack can handle SysV if you choose. And my hardware "just worked" out of the box. Slackware is so smooth that I can actually forget I'm on Linux and just get on with what I'm doing. That transparency is where operating systems need to go. If you forget about your OS, then your OS is doing things right. Kudos, Pat.
For those that think Slackware is outdated, old-fashioned, or too hard to use: think again.
About the author:
Steve Husted is a long-time Linux user and all around computer geek. Steve has 4 computers at his house running Slackware. He likes to rant about Linux to anyone that will listen. Are you listening?
If you would like to see your thoughts or experiences with technology published, please consider writing an article for OSNews.
- "Slacker tries Gentoo, page 1/2"
- "Slacker tries Gentoo, page 2/2"