In exploring a renewed interest I’ve developed in Fluxbox recently, and spurred by some new stuff I learned from reading Patrick’s wonderful Fluxbox tweaking post a couple of weeks ago, I thought I’d do a writeup on another capability that Fluxbox has that I’ve never delved into: dockapps.
Fluxbox has as a part of its toolbox a friendly home on its desktop for dockable utility applications that can provide information, handy functionality, and even dress up the otherwise normally spartan Fluxbox user space. I don’t use many dockapps, but it’s worth using the ones I have as examples in this writeup, if nothing else just to demonstrate how to set this up and take advantage of this capability.
So in this post, I’ll be discussing three dockapps: GKrellM, WMix, and WMWeather.
I was looking around for ideas for something to write up today, so I asked a friend of mine about his most recent Slackware setup experience. He told me, “my sound isn’t working at the moment, but I really haven’t delved into that at all”.
Which got me thinking. This is a common question among people who are using Slackware and aren’t that intimately familiar with it. I know, this has been written up about a billion times, but not here, and it’s a nice basic HOWTO that I think really belongs on Linux Critic.
By popular demand, I downloaded, installed, and worked with the new Hannah Montana Linux distribution, and decided to post a review of this product, as well as some tips and tricks on how to get the most out of this niche Linux distro.
To aid the reader in following this review visually, I have taken numerous screenshots and included them here.
I was able to download the ISO for HMLinux from the Sourceforge homepage of it. I downloaded “v2” of it, using Bittorrent. It downloaded quite rapidly, only taking 15 minutes or so, leading me to believe that it is well-seeded as a torrent.
The ISO is a combination LiveCD and installation CD. I think it’s nice when distro developers/packagers do this, as it gives one the chance to see if the distro is going to work on one’s hardware simply by booting from the CD, and making that determination BEFORE one actually has to install anything to the hard drive.
Continuing with my attempt to document the problems I’ve run into running Fluxbox on top of Ubuntu 9.04 and their solutions, I figured I’d present two more things I’ve encountered and resolved since the other day’s rather annoying touchpad fiasco.
These two were both relatively little things, but they’re the kind of things that tend to drive me nuts. The first was a problem with the screen automatically locking (using Xscreensaver‘s built-in lock function — even though I had all such functions disabled), and the second was an issue with sound being muted and the master volume being set to 0% every single time I rebooted — necessitating my manually unmuting it and raising the volume if I wanted sound every day.
As I had mentioned in yesterday’s post about configuring Fluxbox on Ubuntu 9.04 on my old Toshiba laptop, I had one nagging issue I couldn’t figure out, namely the rather simple fact that the touchpad wouldn’t stay disabled.
I know this isn’t a big deal for most people, but for me it’s a rather vexing one, and it bothered me that I had to manually do so every single time I logged in.
So this afternoon I took a deep breath, did some more Google searching on the subject, and arrived at an overly-complex (but doable) solution.
When I was first preparing to switch to Linux many years ago, I went into research mode and looked around the net a bit. At the time, part of the allure of Linux were the crazy cool desktops people had. After I switched I tried Gnome, then KDE, and was depressed at how uncool and *dozelike they were. Eventually, I discovered that all those amazing desktops were the result of Fluxbox (or the other *box forks). I switched immediately.
To my surprise, I found that not only was I able to get a really cool appearance, but Fluxbox made all the things I wanted out of a window manager, and some I didn’t know I wanted, simple. It turned out that I was not the only user to have noticed those operating system limitations and failings I’d been grumbling about for years, particularly with *doze. The Fluxbox crew apparently knew my pain and had gone about addressing all of those complaints.
When I first started using Linux, I used Red Hat and Mandrake, both of which booted into a graphical environment by default.
One of the first things I noticed about Slackware when I first installed it was the fact that it booted into a command line only interface by default. From there, I had to log in, and if I wanted a GUI, I had to type “startx” and then it’d start X-windows and go into whatever my default window manager was.
I remember being a little confused about this at first; it wasn’t a problem, but I knew there had to be a way to change that. I figured I’d write up a brief few paragraphs on that subject, since I ended up having to dig around the web some at first to figure that out.
In the wars between GNOME and KDE (which now has even split between the two factions warring over KDE4 and KDE3.5), some of the other environments get lost in the shuffle and are often forgotten about.
One which I think is underappreciated is Fluxbox. Based on the original Blackbox 0.61.1 code, Fluxbox is a blindingly fast, simplistic approach to providing a graphical user environment while staying out of one’s way. Easy to use, easy on resources, and easy on the eyes, Fluxbox is an elegant choice that is often overlooked when the options are weighed between other graphical environments on Linux machines.
I started using Fluxbox when I was on some extremely quarrelsome hardware and needed something with a lot less going on than GNOME or KDE so that I could more effectively troubleshoot it. What I found out was that Fluxbox had an extremely tweakable interface… and I like things I can tweak and customize. I also discovered that it ran extremely fast on the limited hardware I had at the time, something else that KDE and GNOME didn’t have.
Intrigued, I stuck with it for a while and over time I learned a few good hacks that I thought I would share with the three or four readers I’ve acquired here.
One Linux topic on which everybody seems to have an opinion is partitioning. “What’s the best way to partition my system?” newbies ask, and if they do so in a public Linux forum frequented by experienced penguin techies, they are bound to get at least a dozen answers, many of them completely different from each other.
So what is the best way? Simple. Whichever way you find works best for you.
When I first started out with Linux, I didn’t know either, and I did a lot of reading on the subject, and as a result I created a partitioning scheme that works best for me, and that’s still more or less what I stick with.
With my recent Ubuntu installation I didn’t do any manual partitioning, mostly because for one, I wasn’t planning on dual-booting that laptop with anything else, and for another, I wanted to accept the defaults so that I could see what Ubuntu does on its own.
However, when I’m setting up a Slackware machine, I have a method that I follow.
One word of caution. If you’re setting up your partitions presumably to hold a Linux installation, write down what you’re designating what (i.e., “hda1 = Windows”, “hda5 = swap”, “hda7 = root”, et al) so that you have it to refer to when you’re installing later. Nothing quite like coming to the point in the install where it asks you “where do you want to mount your home directory?” and you don’t remember which partition you created with /home in mind.
Been there, done that.
So you made a choice of which distro to try, now what?
Sounds like a simple question, but it does come up, even for the more technical folks. “I want to give Linux a try, but I have no idea where to get it, or how.”
When I started out in the Linux world, I didn’t know either. So I’ll help you out with that.
Let’s just suppose for a minute that you took my advice in last week’s post and went with one of the two simple options I suggested, depending on your needs. Good! That narrows down where you have to look to get what you need.
Of course, if you decided to go with some other distro, a great centralized location to start with is Linux.com. From there you can get to most of the major distros’ websites, and from those you can easily find places from which to download whatever you need to your heart’s content.
But let’s go back to the two from last week’s “Which Distro?” post. Slackware and Ubuntu.