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.
Even though the jury’s still out on my opinion of Ubuntu 9.04 on my laptop, I finally had enough of GNOME today and configured Fluxbox on it and set it as my default window manager.
I’m running into some weirdness with that even, however, which may color my opinion of Ubuntu as a result… things that I’m not accustomed to fighting with when using Fluxbox.
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.
I posted a screenshot in my Fluxbox article a month ago, but Fluxbox is just so tweakable and so sharp looking I feel the need to post another screenshot just to illustrate that.
This is Fluxbox v1.0.0 with the “sid_fluxarnation” style, running on top of Slackware 12.1. I don’t recall where I got the sid_fluxarnation style, but you can easily find one like it, among about a billion others by going here or by following any of the other links in the “styles” section at the bottom of this page on the Fluxbox site.
Also in that screenshot, you can see I’m running GKrellM 2.3.1, using the K5-FVWM theme for it which I downloaded from Muhri.net.
As always, if anyone has questions regarding how to configure or tweak their Fluxbox setup, let me know. It’s easier than you might think! Cheers!
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.