|
|
||
Slackware 10.0 Shortcomings—Day 19© Copyright Darrell Anderson. I am pleased with how Slackware 10.0 and KDE 3.3.1 performs on my so-called aging hardware. I haven’t tried running all kinds of software, but the underlying structure seems snappy compared to my Mandrake 9.2/KDE 3.1.3 installation. Not as fast as my NT4 environment, however. I like KDE and intend to stay with that environment. That decision also helps me migrate by avoiding the contentious debate about desktop environments and window managers. KDE is familiar ground for people coming from Windows. With each release of KDE I notice improvements, including speed and response. I understand that KDE 4 will be faster yet. If so, perhaps then the old argument that KDE is too slow for mid-range hardware finally will end. I still recall trying to run KDE version 2.2 on my hardware. Old dogs in August move faster! The simplicity of Slackware grows on me. For the past couple of years while slowly becoming more acquainted with GNU/Linux, I read many mixed reviews and thoughts about Slackware. The simplicity perspective intrigued me from the beginning. I want software that does not get in my way or builds hurdles that I have to get around to control my own computer. My computer is my property—enough said. Despite the steeper learning curve with Slackware, something about which I have mixed emotions, I like the idea that Slackware is “generic” in design. That is, if something happened to the Slackware maintainer (a realistic concern considering that person’s recent illness), the overall design is such that knowledgeable people could continue the basic Slackware design. The Slackware design is such that nobody tries to merge various window managers and desktop environments into a quasi-cohesive product. Although I always have been impressed with the programming abilities of the Mandrake people, I never liked the way they redesigned the original floor plan of how GNU/Linux works. I am no purist, but years of providing technical writing services has trained my eye to discern between simple and complicated designs. The Mandrake people also have done an incredible job of merging the various window and desktop environments into one, but from my experience, have done so at the cost of performance and customization. Perhaps Mandrake version 10.1 is much faster, but I don’t know because I have not tried that distro. I would recommend Mandrake products to people who cannot fathom tinkering under the hood, or do not place a priority on controlling their own computer, but that philosophy is not for me. I don’t want to become a Slackware guru or geek, but nonetheless Slackware does not get in my way. Having previously been exposed only to System V scripts, I find the BSD-style approach much easier and simpler to understand and maintain. Yes, one does need a more intermediate knowledge level to configure Slackware, but right now I am willing to consider that price to keep my system simple. Yet, I remain frustrated, not because of the minimalist approach of Slackware but error messages. I have spent several days chasing and resolving error messages and learning the various ways the Slackware maintainer designed the system. Except to experienced GNU/Linux people, Slackware definitely is not an install-and-run distro and I knew that before I started. However, I grossly underestimated how much tweaking I would have to do and more importantly, exploring. Yes, command line zealots can jump in and not miss a beat after installing Slackware, but not us GUI types. For example, the Slackware distro provides no default global or local bashrc files. I was able to overcome that deficiency by copying my previous Mandrake files. I also had to fine tune the existing /etc/profile script to better suit my needs. This is an area needing improvement. I also noticed there is only one file in the /etc/skel directory. I would think that directory would be filled with example files so when creating new user accounts those files are automatically copied to the new user’s home directory. I realize Slackware is a minimalist distro, but sometimes I wonder about the definition of “minimal.” Another area that confused me was the Message of the Day (MOTD). That is, what I thought was the MOTD. I was confused because the /etc/motd text file contained no information other than the kernel version number. From where were these cutesy messages being derived? Eventually I discovered the messages were being generated from a BSD games package called Fortune. That program is invoked from the /etc/profile.d/bsd-games-login-fortune.sh script. I do not mind the messages—they are short and often humorous breaks in the day, but being unable initially to discover the source was frustrating. The MOTD and these interactive shell messages are not related, a confusing point to people unfamiliar with the Fortune program. The Slackware documentation could provide some better clues about this process. Some people will notice I have yet to create a user account. Thus far I have been working exclusively as root, and yes, gasp(!), within a GUI too! Please don’t try preaching to me from some white ivory tower about using the root login account. I’ve been logging in as “root” on all of my computers for more than twenty years—before some of you were born. Additionally, during this migration transition, I do not have the time or patience to play the login and security game and “su root” every time I want to make changes. I want changes and I want them fast. This setup is not connected to the internet, is used only by me, and I am well aware of how “easily” I could destroy the entire installation (roll eyes). I am in exploratory mode right now, not production mode. The computer “newbie” might need to hear precautionary priesthood incantations against logging in as root, but I don’t. I won’t listen to those comments! That’s my risk. I’ve been around computers for more than two decades and I accept those risks. When I get things functioning as I want then I’ll login as a regular user and play the “su root” game! Finis. |
||