So I keep ranting about Firefox here, and for good reason: the Mozilla team is going above and beyond the call of duty when it comes to driving users to other browsers.
However, try as I might, I simply encounter too many dealbreakers in Chromium.
When I think about it, the last version of Firefox that didn’t drive me crazy with crashing, incompatible add-ons, and stupid UI changes and features removed, it would have to be Firefox 3.6.
I keep forgetting how to do this, so I’m posting this here as much for my own reference as for anyone else’s. This is how to downgrade newer versions of Firefox to 3.6 and keep it that way, at least until things settle down a little, or until another browser comes along that can actually be a viable replacement for it — unlike newer versions of Firefox, sadly. This works with Mint 11, which means it will also work with Ubuntu 11.04.
Breaking with past tradition, the Linux Mint folks have done away with “Community Editions”, instead bringing the non-Gnome flavors of Mint fully under the Mint umbrella. Linux Mint 9 LXDE is now in general release. Here are my thoughts.
What do you get when you combine the flexibility, versatility and ease of maintenance of Ubuntu, the blinding speed and simplicity of LXDE, and a focus on social media and the cloud?
You get Peppermint OS, that’s what! Brought to you by the same developer responsible for Linux Mint 8 LXDE Community Edition, and for resurrecting Linux Mint Fluxbox CE as well, Peppermint OS is a lightweight, fast, stable implementation of what Kendall Weaver’s vision of the perfect Linux distro might be for speed and the web.
And I think he’s onto something.
As some of you may know, a few weeks ago I posted about my efforts to revive aging laptop hardware. While there is still a bit of work to be done, the bulk of the project is complete, and the rest is simply detail work and optimization for our particular work environment.
At my office, we have a pair of old laptops purchased back in 2003 or 2004, which are terribly slow, woefully underpowered and horribly outdated, but which we still use periodically. In other words, they made a perfect target for an OS makeover.
Anyone who has run Windows XP on a P4 with 256MB of RAM should be able to appreciate just how sluggish these machines are. So with my boss’s blessing, I gathered the two machines and tried to breathe some new life into them.
I am always on the lookout for a new way of doing things when it comes to personal computing, and one of the best ways to do so is to experiment with different window managers for Linux.
Since I have my laptop set up as an Ubuntu test platform, and since APT makes it easy to download and install applications and not find myself in dependency hell, my laptop seemed to be a great way to play around with a window manager about which I’ve been reading for some time: Openbox.
Those of you who are familiar with LXDE will have some experience, albeit limited, with Openbox, as LXDE is based on it (with a bunch of other cohesive applications and a consistent look and feel integrated to complete the transition from “window manager” to “desktop environment”), but Openbox will seem much more familiar to users of Blackbox and Fluxbox, predominately in the sense that Openbox is built very light and minimal, with a desktop bare of icons, and a user-defined right-click menu that is used for launching applications. Like Blackbox and Fluxbox, Openbox is also dockapp friendly, and as a window manager it runs very fast on limited hardware.
I’m a big fan of Fluxbox, so I thought it worthwhile to give Openbox a try, if nothing else to give me material for a Linux Critic writeup, and instead I found that I just liked using Openbox, so this turned out to be more than just a review.
DISCLAIMER: Be prepared. There is whining ahead. I want to preface this by saying that I’m not interested in having a discussion about why I don’t gush with love over KDE 4, and I’m not particularly interested in suggestions for forcing it to work for me. This post is more about me wrapping my head around planning for how my use of Linux is going to change now that I’m going to have to re-think a lot of things about what has been my favorite Linux distro for years.
Why I’m disappointed
I guess I probably shouldn’t be too surprised, because I knew that Pat Volkerding has been working with my least favorite desktop environment and it’s been in
/current for a while now.
But I guess a part of me still was holding out a childish hope that KDE4 was going to be included in
/testing only, and that the default version of KDE for the Slackware 13.0 release would be KDE 3.5.10, the last decent release of that desktop environment. Given Patrick’s tendency to play it safe in regular Slackware releases and stick with only stable, fully-developed and thoroughly tested applications and desktop environments, I would have thought that something like KDE 4 — a desktop environment that’s still easily a year’s worth of hard development away from being a suitable replacement for KDE 3 — would be back-burnered in Slackware in favor of what is known to work and work well.
I probably shouldn’t be upset about this; it’s Linux… if I don’t like it, I can just make my own distro, right? If I want to spend the hours and hours it’ll take for that, sure. Well, I’m not to the point of making my own distro yet. But this does mean I’m going to have to significantly change my Linux usage, starting with replacing a bunch of stuff.
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.