Matthew Edward Liston

An interesting news item: Due to changes in Mozilla’s support cycle (support for Firefox 3.0 is ending), Ubuntu will be backporting FF3.6 to Hardy, Jaunty, and Karmic.

This is an interesting shift in Ubuntu’s update/backport policies. Curious to see if other distributions will follow suit…

https://lists.ubuntu.com/archives/ubuntu-devel-announce/2010-June/000719.html

I recently had the opportunity to collaborate on a website and online gallery for artist Sharon Wybrants.

http://www.artbysharonwybrants.com

It was an honor to work with this very talented artist!

Read my latest article on Green Chi Cafe!

Advanced Power Management

Here are a few tracks from my most recent studio project, playing bass for an instructional book/CD package by my friend Burgess Speed. Burgess was my (very patient) editor on last year’s The Total Blues Bassist project, so it was a pleasure to return the favor and help with his CD. It’s called The Beginner’s Guide to Electric Guitar and it’s available through National Guitar Workshop Publications.

I know from personal experience that it’s not easy to write original examples “in the style of” the classics. Burgess did a great job capturing the essence of these examples without ripping them off note for note. See if you can name the tunes; first person to respond correctly (in the Comment section below) gets a gold star!

Listen to The Beginner’s Guide to Electric Guitar.

ps Yes, that is Pete “Cowbell” Sweeney on the drums!

Eat Fresh!

(This is part 2; the 1st part is here.)

Okay, so hopefully by this point you understand the importance of repositories for running a stable Linux system. You’ve gotten into the habit of checking the repositories first when adding new applications (instead of the “Windows Way” of surfing the web looking for apps). Sooner or later, though, you’ll run into an issue that often confuses new Linux users: “outdated” application versions in the repositories.

Most Linux distributions fall into one of two categories: “rolling release” or “time-based release.” Understanding the difference (and choosing the correct solution for your needs) is key to an enjoyable Linux experience.

I’ll start by explaining rolling release. The goal of rolling release is to keep its users’ systems up to date through a constant stream of updates. When a new version of application like Firefox is released, it appears in the rolling release repositories fairly quickly (usually a matter of days). Rolling release users get the new Firefox the next time they update their systems. Rolling release distros are the best choice for users who want to install once, then keep their system up to date with the latest applications as soon as they are available. Arch and sidux are two of the best-known rolling-release distros.

Timed releases are the opposite. The repositories of timed releases are “frozen” at a certain point, meaning users do not get new application versions as they become available, only minor updates (bug fixes and security patches). Rather, users are expected to upgrade everything at once, at a regular interval, by moving to the next timed release of the distribution. For example, a new Ubuntu comes out every six months, and all major updates are “grouped together” into the new release, rather than being made available retroactively to users of the old release. Ubuntu, Debian Stable, and Fedora are examples of time-based releases.

Remember how we talked about the “Windows Way” in Part 1? Because there’s no unified repository or update system for Windows, its users are accustomed to a hodgepodge of application versions. For example, a typical Windows user has the 2001 version of Windows (XP), 2010 version of Firefox, 2008 version of iTunes, and 2003 version of Office. What a mess! It’s no surprise Windows users get confused by the “Linux Way.”

Here’s an example: In June 2009, Mozilla released version 3.5 of its popular Firefox web browser. At that time, the current Ubuntu release was 9.04 Jaunty Jackalope (9.04 = April 2009), which included Firefox 3.0. The Ubuntu Forums were flooded with users asking “I just updated my system, but Firefox is 3.0. When will I get Firefox 3.5?” The answer, of course, is “never,” which confused and irritated a lot of users. (Note: In the end, Ubuntu actually did provide a ‘firefox-3.5′ package, codenamed ‘Shiretoko’ to its 9.04 users; an exception that proves the rule.)

“OMG, Ubuntu sucks, why would I use such a horribly outdated operating system?” (Never mind that you were happily surfing the web with FF3.0 a month ago; did it suddenly stop working just because a slightly newer version is available?) Rather than take a few minutes to understand how a time based release works, many of these users said “rolling release must be better” and switched to Arch, only to come crawling back to Ubuntu eventually. Rolling release might sound better on paper, but in the real world, timed release distros (Ubuntu, Red Hat, Mandriva, Debian, etc.) are much more common. How could this be?

The advantage of timed release (for many users) is it helps us understand Linux as a whole, rather than the sum of its parts. Because each release cycle has a frozen set of applications, everyone using the same release has an identical system (well, more or less). Instead of thinking “Linux kernel 2.6.28, Firefox 3.0, Gnome 2.26, etc.” you can simply think “Ubuntu 9.04.” All of the applications have been tested to work together in those specific versions, resulting in a stable system with no unexpected major upgrades that might “break” your system. When a new release comes out (the current Ubuntu is October 2009’s 9.10 Karmic Koala), all of your apps are upgraded at once, to newer versions that have all been tested to work together.

Now here’s where things get really interesting. Depending on the goals of the project, each distribution has its own development process and release cycle. Finding a distro whose goals match your own is a magic moment in discovering Linux. Ubuntu, for example, has a new release like clockwork every 6 months (April and October), and each release is supported with bug fixes and security patches for 18 months. Debian, on the other hand, is quite similar to Ubuntu, except that they release “when its ready,” roughly every two years and support each release for several years. Ubuntu’s approach is great for average users who want relatively up-to-date applications (never more than 6 months old), while Debian’s approach is more for users who want an ultra-stable system and don’t mind using slightly older applications. At the far extreme is Red Hat Enterprise Linux; their releases include only older, well-tested applications, but they support each release for seven years! Corporations pay big bucks for Red Hat because they need this support, not flashy new features.

Now personally, I don’t think there’s a clear winner in the battle between rolling release and time based release. I use a time based release on my work desktop (for the stability), but rolling release on my laptop (because I like playing with the latest new applications). In a future article, I will attempt to answer the “which distro is right for me?” question in greater detail. But for Average Joe who just wants a user-friendly home operating system, my advice is, install Ubuntu, and don’t worry if you don’t get the latest Firefox the same day it is released. You’ll never have to wait more than six months, and in the meantime, you’ll enjoy the benefits of a stable system.

Now, does this mean you can’t use the latest version of Firefox (or any other application) in a time based release? Of course not! You can add a 3rd party repository (PPA) to your software sources, compile the application from source, or download the latest version right from the Mozilla website. But ask yourself why you think you need it. There are plenty of good reasons (your boss sent you a Microsoft Office document in .docx format so you need the latest OpenOffice), but if you are simply stuck in the “newer is always better” mentality, I invite you to graduate from the “Windows Way” and enjoy the stability of the “Linux Way.”

Check out my new article on eCycling your old computer!

One topic I didn’t have space to delve into is your data security when you sell, donate, or recycle an old computer. Even if you’ve deleted your sensitive files (personal information, banking details, embarrassing photos), a clever hacker can recover them from the hard drive. There are only two safe solutions, in my opinion:

1. Remove the hard drive from the computer (and keep or destroy it). Sell/donate the old computer “as is” without a hard drive, or be nice and install a brand new hard drive for the next user (you can get brand new hard drives for under $50 these days).

2. Use a utility to “zero out” the hard drive, completely destroying all existing data. I’ve had good luck with the Linux command ‘dd’, but for true peace of mind, check out applications like DBAN.

Be especially careful if you are donating your computer to a school… kids today are very good at figuring out this stuff!

In the process of helping new Linux users over on Ubuntu Forums, I see a lot of the same questions coming up again and again. Many of these questions can be traced back to one uber-question: “What is a ‘repository?’” Understanding the answer will clarify the “Windows Way” and “Linux Way” of finding and installing software. While I come from an Ubuntu background, these same concepts hold true for many other distributions (or “distros”) like Debian, Fedora, or Arch.

Let’s begin by describing what a repository is not: the Windows Way. How do Windows users get new software? The first “tier” is the software that comes pre-installed when you bought your computer: the operating system, web browser, system utilities, etc. The second tier is “boxed” commercial software you buy and install from a CD/DVD (Office, Photoshop, etc.). The third tier is software you install by downloading an .exe installer from a website. Software in tier 3 ranges from well-known commercial apps (Firefox, iTunes, OpenOffice) to obscure “shareware” (games, CD rippers, video converters). The 4th and lowest tier includes all sorts of malware and viruses, as well as pirated commercial applications.

In summary, the Windows Way is not really a “Way” at all. Software can come from a wide range of sources, and each application has its own installer. There is no unified mechanism for upgrading all of your apps together, or of resolving conflicts and dependencies. Depending on the choices you make and the risks you’re willing to take, you can have a stable Windows system or a “blue screen of death” Windows system.

Can Linux users follow the Windows Way as well? Yes, and it is easier than you may think. If you want the latest Firefox for Linux, you can simply go to the Mozilla Website and download it. (tar.bz2 is an archive format like .zip in Windows; in most Linux distributions, you can simply double-click the archive in your file manager to extract it.) Also, just about any Linux app can be “compiled” yourself using the source code from its developer. So, it is indeed possible to use Linux without ever touching a repository. But…

Most Linux distributions (and oftentimes, each separate release, such as Ubuntu 9.10) have one or more repositories or “repos”. A repository is a tested, secure (by way of a “key”), and easy-to-use software source. Repositories can be stored on a CD, DVD, or a local network server, but for most home Linux users, they are accessed through the Internet. Distributions include various tools for installing applications or “packages” from these repositories (Ubuntu has the Software Center, Synaptic package manager, and various terminal commands).

The Linux Way (as I see it) is to trust these repositories. This is a two-part process: First, use the repositories to maintain your system over time. If you run your update manager regularly, you’ll be up to date on bug fixes and security patches for every application on your system. Make sure you keep track of your repository’s expiration date (Ubuntu 9.10 reaches “end of life” in April 2012 for example) so you can upgrade to a newer release in time. Second, use the repositories as your default source for installing new applications. If the application you need is already in the repositories, installing it is usually an easy one-step process.

If you can’t find the application you need in the repositories, the first question you should ask is “why not?” Sometimes, it’s because the application is Windows-only! This doesn’t mean you can’t use Photoshop in Linux (there are ways), but the Linux Way is to find a free, open-source alternative. Check out GIMP for photo editing, or Rhythmbox as an iTunes replacement.

Other times, an application you need is available for Linux, but isn’t found in the repositories for your distro. It might be deliberately omitted (for example because it doesn’t fit the distro’s philosophy) or might simply not be on the distro developers’ radar screen (often the case for niche applications). Assuming that you trust the application’s developers, this is the one instance where I would recommend installing from outside the repositories. You can usually find instructions on the homepage for the application. It may be as simple as double-clicking a .deb, or may involve adding a third-party repository to your software sources (be very careful doing this, and be sure to get the key). I consider responsible use of third-party software to be compatible with the Linux Way.

A special case arises when the application you need is found in the official repositories, but it is an older version than you would like. A good example is the OpenOffice.org version (2.4) found in the current Long Term Support release of Ubuntu (which lacks compatibility with newer Microsoft formats). Stay tuned next week, and I’ll share my thoughts…

Graphic photos, not for the faint of heart!

What’s the solution? Bust the dust at The Green Computer.

I recently had the the opportunity to play bass for two Jamaican music CDs. Guitar Atlas: Jamaica by Raleigh Green and Drum Atlas: Jamaica by Pete Sweeney are instructional book/CD sets all about the musical history of Jamaica. From mento to dancehall, I really learned a lot of interesting beats and styles for these sessions. Raleigh and Pete were my backing band on the Total Blues Bassist project, so it was cool to return the favor.

Here are a few selected tracks from each CD, for your listening pleasure. Both are available through National Guitar Workshop Publications.

Guitar Atlas: Jamaica by Raleigh Green
Drum Atlas Jamaica by Pete Sweeney