Recently in Free, open-source software Category

This post began its life as a comment on the previous Sparcstation 20 entry, and true to the way I overwrite even a comment, it works well enough as a standalone entry.

And thus, here it is in that form:

I've discovered that NetBSD doesn't run so well on the Sparcstation 20 (50 MHz processor, 128 MB RAM). The install went fine, but the X configuration was less than optimal. Console messages continued to appear on the X screen, and I could tell that, among other things perhaps, the horizontal sync and/or vertical refresh might have been just a bit off. I imagine that if I take the xorg.conf information from OpenBSD and use it for NetBSD, all issues will be solved.

But when NetBSD's 32-bit Sparc packages for Firefox and Seamonkey (precompiled packages, NOT ports) wouldn't install, and then the Geany package did install but ran so slowly as to be unusable, I decided to go in a different direction.

Thus far, that direction is a reinstall of OpenBSD. I haven't tried any ports yet, but all the packages I have installed — a few GUI editors (nedit, which I quite like, and another I can't remember), plus the Dillo browser, which in all fairness ran great in NetBSD, too — did work.

Now that I'm running not the box's original, jet-plane-noisy 2 GB Seagate hard drive but a super-cheap-on-eBay 35 GB Hitachi SCSI drive that's pleasantly quiet, maybe the installation of an OpenBSD port of a "modern" Web browser will work. Maybe not. I'll also try to roll Abiword onto the box, as well as Geany (for comparison's sake, if anything else).

And there's always Solaris.

I know there are Solaris-compatible packages for just about everything, so if I can't manage to get Seamonkey or Firefox installed from OpenBSD's ports with the extra disk space, my next move will be installing Solaris 9 (I got an unopened box of the software for $1 — yep, that little, plus shipping — on eBay) and see how that OS runs on the box.

One thing: Sound on the 32-bit Sparc platform doesn't work in OpenBSD. It does in NetBSD. Of course it does in Solaris, since Sun's OS was written with the Sparc in mind.

It may be that Solaris is the best OS for desktop use on the Sparc 20. Probably the best thing to do is get a CPU module faster then the current 50 MHz processor I'm now running, and also upping the memory to the max of 512 MB (right now I have the 128 MB the box had when I got it).

But make no mistake, for sheer out-of-the-box configuration on a Sparcstation 20 (sound nothwithstanding), OpenBSD is way ahead of NetBSD.

My next line of attack is trying a few (or more) OpenBSD ports. Even if this experiment goes well, I'll have to roll Solaris 9 onto the Sparc 20 before I decide on any long-term OS for the box.

Before I finish this entry, it's worth pointing out that Debian Etch for Sparc boots but won't install. It hangs when trying to load the CD driver. I don't know if the Sparc port of Debian is broken for EVERY 32-bit Sparc model, but it sure doesn't work for the Sparcstation 20.

Image above right: This isn't my Sparc; it's a Sparcstation 5 from http://www.computermuseum.org.uk. They look exactly alike (and in many ways are).

Come to the Jan. 27 meeting of TUGNET — The User's Group Network — and hear me speak to whoever shows up.

My topic: Evolutionary computing: Making the leap to free, open-source
applications and operating systems.

What I'll be trying to do is bring the worlds of this blog, which explores the inner reaches of my own geekiness, with that of my print column, Tech Talk, which is aimed at a more general audience.

Both the blog and column draw heavily on my own experience, and I wouldn't have gotten wherever it is I am now if I worried about what I didn't know. I've said on many an occasion that I'm hear to learn and to demystify the process of wading into the technological waters.

Enough of that. What I'll be talking about is my own journey from a garden-variety user of proprietary software to one who aims to use free and open-source solutions wherever possible.

While I burned and ran my first Linux live CD in January 2007, I first got my feet wet in the world of Unix way back in the 1980s through a free on-campus account at UC Santa Cruz, where average (read: non-technically inclined) students were encouraged to use Unix to write and print out (on a bona fide networked laser printer ... and this was right around the time Apple released its original LaserWriter at a cost of $6,995) our essays and anything else we did for our classes.

At TUGNET, I'll talk about the advantages of using free, open-source applications in proprietary environments like Windows and Mac OS and how that makes it all the easier to make the transition to FOSS operating systems that include a few hundred active Linux distributions and four key BSD projects.

I'll be providing tech tips, as well as book and Web-site recommendations on how to learn more about free software, and I'll talk about why I'm using OpenBSD these days more than Linux (and why that could always change because I'm a major proponent of choosing and freely changing both hardware and software to best do the task at hand).

I'd like to thank TUGNET president Marian Radcliffe for inviting me.

And dear reader (as I weakly invoke Jane Austen), I hope to see you there.

Here's the deal. I've been using one of my two nearly identical Toshiba 1100-S101 laptops for a growing share of my day-to-day work, and not just at home.

The degradation of my Windows XP-running Dell box over the course of the day (OK, it's not that great in the morning after a fresh boot, either) has driven me to use my older, slower laptops, which under non-Windows OSes actually do things better and faster.

I basically resurrected both Toshibas from death in the form of recycling, which is what would have happened to them had I not pulled them from the haul-me-away pile. Both had XP installed. Until this point, I didn't have any personal machines running XP, and if you don't count the Windows 2000-running Pentium II box I rarely turn on, these are really my only Windows-running PCs I use besides my main work box — the one that barely works.

Think of that last paragraph as somewhat of an explanation for why I'm dual-booting both laptops, the first into OpenBSD 4.4 and the second, as of this afternoon, into Ubuntu 8.04 LTS. I really have little use for Windows, but in the course of whatever it is that I do in these blog entries and my print column, I just might need a Windows machine. Or not. Since I can't reinstall Windows XP whenever I wish due to not having an install CD, I'm leaving those now-shrunken NTFS partitions intact until I decide a) I really need the disk space or b) figure out how to get the hard drives out of the Toshibas and put them aside in the unlikely event that I absolutely need to run XP some time in the far future.

(Yes, I do have the OpenBSD T-shirt with this design. It doesn't get more geeky.)

I'm getting ready to give the $0 Laptop (Gateway Solo 1450) to our daughter to run her educational games (Childsplay, Gcompris, TuxPaint) on Ubuntu Hardy with the non-crashing Xfce window manager instead of the crashy version of GNOME in this Ubuntu build.

To replace that machine for me, I pulled a Toshiba Satellite 1101-S101 laptop from the boneyard.

With a 1.3 GHz Celeron processor, 248 MB RAM (how it has this amount, I don't know) and a 20 GB hard drive, the specs are pretty similar to the Gateway, except for the Gateway's 1 GB of memory, which I'll probably split between the two machines.

The Toshiba came to me with Windows XP, and this time I wanted to preserve Windows and dual-boot it with a FOSS OS. The CD/DVD drive is extremely flaky. I think it's dying. It does better with "commercial" CDs, and I did get it to boot Partition Magic so I could shrink the NTFS Windows partition and set it up for Linux.

The only Linux CD I could boot was Debian's Etch and a Half. Something was squirrely on our network, and I couldn't get DNS working in the installer. I could've done a minimal install, fixed /etc/resolv.conf and then brought the rest of Debian into the box, but I took this opportunity to go in a different direction.

With all the CPU fan issue on the Gateway, I could never run OpenBSD (or NetBSD or even FreeBSD after the first boot) because I couldn't get the noisy CPU fan under control.

I powered up the Toshiba, which couldn't get networking in Windows either. Since I don't yet have the administrator password, I couldn't update the DNS settings.

I went to an OpenBSD mirror and downloaded a floppy image plus a DOS/Windows utility that helped me create a bootable OpenBSD install floppy. (Before anybody mentions this, I know I could've just as easily created a Debian boot floppy.)

The Toshiba successfully booted off the OpenBSD floppy, and I was able to plug in a mirror and do a full install over the network.

This was my first dual-boot install of OpenBSD, and after the install was done, the machine wouldn't boot at all. I hadn't installed a bootloader and thought the box would boot into Windows, where I planned to modify that bootloader to choose between Windows XP and OpenBSD. Instead I got a "no operating system" message.

And I don't have a Windows XP disc from which to "repair" the master boot record.

So I rebooted with the OpenBSD floppy, dropped down to a shell and added the OpenBSD bootloader at the prompt:

# fdisk -u wd0

Then I rebooted and was in OpenBSD. There is a GRUB package for OpenBSD, and I'll probably install that so I can easily dual-boot either Windows and OpenBSD or eventually Linux and OpenBSD. There are other alternatives as far as bootloaders go, but my familiarity with GRUB is what is governing my decision in this case.

I'm also going to add rsync as well. I have no skills when it comes to OpenBSD's dump and restore utilities, so having rsync is another plateful of Linux-like comfort food that will help me get along in OpenBSD.

Other packages I've installed thus far: nano, mc (the Midnight Commander file manager), Rox-filer (my favorite X file manager), Geany (X text editor) and the Firefox (I probably should've gotten the version with Java, but I'm going to try to add the Java developer's kit and get the Java runtime that way) and Opera Web browsers.

Opera came via a port and not a precompiled package, and it took a lot longer to install this time than the last time I installed it in OpenBSD (on the Compaq Armada 7770dmt), if I recall correctly.

When you download the ports tree and install from there, everything is fetched for you and compiled when needed. Looking at all the output in the terminal, it looks like these ports could never work, but in my experience with OpenBSD they always do. This time was no different. It took maybe 45 minutes to get all the dependencies plus Opera, but after that it worked immediately.

I've grown accustomed to OpenBSD's default window manager, Fvwm2, and I'll probably stick with it for at least awhile before adding any others. Unlike Debian, Ubuntu, Slackware, etc., installing an app in OpenBSD doesn't automatically update the menus, so you have to manage this yourself. Getting into the guts of the .fvwmrc file is more instructive than not, and once I figured out how to do it, it got less arduous.

I still don't like waiting for ports to download, compile and install, so having 4000+ precompiled packages for i386 is a very good thing.

After a year of strugging with and complaining about the Gateway fan blasting away under OpenBSD, I couldn't believe that I was running OpenBSD 4.4 on the Toshiba with no CPU fan problem whatsoever. Everything from autoconfiguration of my two network interfaces (one Realtek 8189 wired Ethernet, the other an Orinoco WaveLAN PCMCIA wireless) to a perfect xorg.conf made this OpenBSD install go .

I haven't checked audio yet, but I've never had OpenBSD fail to configure the sound card.

I've always read that most OpenBSD developers use laptops to code in the OS, and now that I have this Toshiba running OpenBSD better than anything I've tried before, I'm amazed at how well it installs and runs on this specific platform.

I've probably written a half-dozen posts about exactly why I'm running OpenBSD, and I'll probably write another one as time allows in the week ahead.

And I'll be either ordering a CD set or contributing directly to the OpenBSD project in the days ahead.

Maybe you're curious about how The Self-Reliant Thin Client is doing.

Here's the uptime output:

steven@maxterm:~$ uptime
13:08:07 up 24 days, 21:15, 2 users, load average: 1.70, 1.32, 1.31

Yep, the VIA C3 Samuel (rated at 1 GHz but running in Linux at 500 MHz for some reason) based converted thin client, running Debian Etch from an 8 GB Compact Flash card, has been working continuously for about a month now (I did reboot a few times during this test for kernel updates).

It's still no speed demon but handles the GNOME desktop fairly well. I did add Fluxbox for testing purposes, and I also installed the lightweight Dillo Web browser, but I'm still relying on the Iceweasel (unbranded Firefox) and Epiphany (GNOME's Gecko build) browsers, plus OpenOffice 2.0 Writer (works surprisingly well, even with 256 MB of RAM and 500 MHz of CPU) and GNOME's GEdit text editor.

I even used CUPS (The Common Unix Printing System) to set up a printer the other day. Even though most systems include native printer-setup utilities (GNOME's is extremely primitive), I find it's both easier and more instructive to use CUPS directly via a Web browser. For those who have never done it, open a browser and go to the following URL to access the CUPS interface:

http://localhost:631

I usually click on Administration and go from there. If you're asked for a login, that login is generally root, with the password being root's password. I can't remember how this goes in Ubuntu, which doesn't let the users (even the main user) at the root password (if there even is such a password).

Ubuntu's root/sudo situation is another kettle of fish for another post, but for most of us, the key to CUPS is using the root login and password to add or modify printers.

I will close out this entry by praising Debian Etch for being so solid on this (and just about every other) platform.

Here's the deal: I've been fighting with Debian Lenny for months on The $0 Laptop (Gateway Solo 1450), where I have everything running great except for my persistent problem with screen refresh in X. I've replaced the Intel i810 driver with the plain Intel driver, I've tweaked everything that can be tweaked in xorg.conf.

I can't really get work done while my display is slowly disintegrating during the course of a computing session.

I'm already running Ubuntu 8.04 LTS as the main distro on this system, and I've been thinking about what to do for the second distro. I'd go back to Debian Etch, but I had problems with the speed of the USB-connected mouse vs. the Alps touchpad, plus problems controlling the touchpad on its own.

In Lenny, the problems I've dealt with (and mostly solved) over the past six or more months have included suddenly disappearing sound (fixed with manually installed ESS Allegro modules), and an Epiphany browser that would always start in offline mode (fixed with a modification to Gconf2, if I have the name of the app right).

Nothing major — and nothing that couldn't be fixed with some help from either the bug reports themselves or other helpful people on the Web.

But this screen-refresh problem persists. I keep hoping that a routine software upgrade will take care of it, but that hasn't happened in countless xorg, driver and kernel updates. I don't think it's going to happen, either.

If you're running something that's very popular that catches the attention of developers (like the Asus Eee PC), chances are good that issues will be resolved. But I can't imagine any developers anywhere are paying any attention whatsoever to my 2002-era Gateway laptop. I'm no C hacker, so there's nothing much I can do, either.

I love Debian. I'm running two newish Etch installs right now (one PowerPC, one i386), and I could very well add a third with my $15 Laptop (Compaq Armada 7770dmt), or even more to a couple of testing desktops I have waiting in the wings. Whenever Lenny goes Stable, Etch will have another year's worth of patches as Old Stable before it reaches its end of life.

Etch has been great, and Lenny has made dozens of improvements. But this one regression has made it very hard to keep my favorite distro on my main laptop.

So I have been thinking for months about what to do, all the while hoping that I could fix the X problem in Lenny.

First of all, I need to rewire the power supply plug. I think that is what is responsible for my intermittent freezes in Ubuntu (which don't seem to happen in Lenny, for reasons unknown). When I have the laptop on a desk, it never freezes, but when it's on my actual lap, as it was when I was trying to work on last-minute election programming yesterday morning, those freezes can really throw me off. I moved over to Debian, but I needed the Java runtime, didn't have it installed and didn't have the time to do that.

And then there's the video issue.

So I've been thinking, what should I install in place of Debian Lenny? I'm a big fan of long-term support releases, especially for older hardware, so I strongly considered CentOS 5, a clone of Red Hat Enterprise Linux 5. But the relative lack of consumer-oriented software had me worried. I could add the Dag Wieers repositories to deal with that issue, but even that repository doesn't cover everything I need.

Mandriva is also on the table, as is one of my favorite distros, Wolvix. The Slackware 11-based Wolvix is due for a new version soon. While its package mix addresses most of my issues, there are a few things that I can't easily find for it. And I worry in Wolvix's case (as well as Slackware's in general) about how long the kernel goes without getting patched.

I almost never see new kernels for older Slackware releases. I don't know if that's because they are unnecessary, but with patched kernels rolling into Debian and Ubuntu fairly regularly, I wonder why Slackware does things differently.

I'd run "regular" Slackware, but I had quite a bit of trouble getting X configured, and I'd rather use GNOME than KDE. I know there are GNOME projects for Slackware, but what I'm trying to do is install something that works well, comes together easily and has lots of available packages.

Given all the Mandriva fans on LXer, I considered it. I've used the Mandriva-derived PCLinuxOS and thought highly of it — and I may in fact go that way. The 2.6.18 kernel in PCLinuxOS 2007 (Debian Etch is also built on that kernel) is perhaps the best ever for the Gateway in that it controls the CPU fan with no intervention. The intervention needed in other kernels is slight (a single line in /etc/rc.local usually does it), but it's nice to have it done automatically.

Again, I'm not a huge fan of KDE, and I find that distros that are either KDE- or GNOME-centric tend to treat the other desktop environment as something of a second-class citizen.

I've had Fedora in the back of my mind for a while. Seeing all the packages available is very encouraging. And the Fedora community looks like a very good resource in terms of getting things working. I imagine that quite a bit of RHEL information would apply to Fedora as well, giving the distro an even deeper bench.

I'm not crazy about the length of support for a given Fedora release, which looks to be 12 to 13 months. I'd feel better with the 18 months that Ubuntu's non-LTS releases get, or even a full 2 years. Compromising on length of support is something I'm willing to do at this time for something that potentially gives me all the packages I want and that runs well besides.

As far as the availability of packages goes, Fedora acquits itself well. I have run it from the live CD before, and it seemed to do well on the Gateway.

In a slightly related matter, my install of Fedora 9 on my Power Mac G4/466 didn't go so well. The X configuration was horrible, and the distro ran much slower than Debian Etch on the same hardware. And Debian did a perfect X configuration for the internal graphics card and huge LaCie electron22blue monitor. Sure I could've used the information from the xorg.conf in Debian to properly modify the same config file in Fedora, but with such a performance hit, it didn't seem worth it.

Since the 1.3 GHz CPU and 1 GB of RAM in the Gateway offers much more power than the 466 MHz and 384 MB in the G4, Fedora seems to run fine on the faster machine.

And now that I have the Ubuntu LTS as my main distro (and hopefully a trouble-free one once I replace that shaky power plug), it's time to try something else.

First I need to keep copies of the xorg.conf, my CPU-fan script and rc.local from Debian Lenny in case I do a reinstall. Then I need to back up the /home files and consider adding a separate /home partition for the secondary distro (Ubuntu already has a separate /home partition).

Again, I'm not happy about the 13-month life cycle of any given Fedora release, and I really don't need a cutting-edge kernel for my not-cutting-edge hardware (unless, of course, it makes a cheap wireless adapter work), but with /home on its own partition, and Fedora installing GRUB on the root partition instead of the master boot record, with the GRUB on the MBR chainloading to the Fedora partition, it shouldn't be hard to roll Fedora out and something else in.

I could change my mind ... or not.

Update: OpenSUSE offers about two years of support per release, and that is enough to get me interested.

I'm downloading new OpenSUSE 11 and Fedora 9 ISOs now, and I'll burn them in the morning.

Upon seeing 17 software updates waiting for me on my Debian Etch box this morning, I hurried over to the Debian security site and learned that the Debian security team issued a flurry of patches on Oct. 29, 2008, for all versions of OpenOffice.

On my system, this is a relatively huge 101 MB download.

The details are available at Debian.org and in the debian-security-announce mailing list:

Several vulnerabilities have been discovered in the OpenOffice.org office suite:

CVE-2008-2237

The SureRun Security team discovered a bug in the WMF file parser
that can be triggered by manipulated WMF files and can lead to
heap overflows and arbitrary code execution.

CVE-2008-2238

An anonymous researcher working with the iDefense discovered a bug
in the EMF file parser that can be triggered by manipulated EMF
files and can lead to heap overflows and arbitrary code execution.

For the stable distribution (etch) these problems have been fixed in
version 2.0.4.dfsg.2-7etch6.

For the unstable distribution (sid) these problems have been fixed in
version 2.4.1-12.

For the experimental distribution these problems have been fixed in
version 3.0.0~rc3-1.

There are some cases when a security patch will go to Debian's Testing branch (currently Lenny) at the same time as the other branches, but in this case, it appears that the patches will be "tested" in Sid and will shortly flow into Lenny (the usual path for software in Debian.

As always, in a default Debian desktop installation, the updates will be pushed to the system in the Update Manager. Otherwise, you can use Synaptic in a graphical environment, or at a console apt or Aptitude to apply the patches.

While Ryan Naraine of ZDNet says that the vulnerabilities don't affect OO 3.0, but Debian appears to be doing patches to that version anyway.

More on Debian security:

• Debian User Manuals (and the Securing Debian chapter)
• Debian security FAQ

I decided to start adding apps to the Self-Reliant Thin Client, which is running Debian Etch from an 8GB CF card as the boot drive with a 1 GHz VIA CPU that insists at running at 500 MHz, plus 256 MB of RAM.

I used aptitude to add the Geany text editor and the Fluxbox window manager.

Fluxbox runs great, as usual, but I really don't see any app-speed improvement with Iceweasel, OpenOffice, Geany or Gedit.

In previous tests, I saw a real advantage to using Fluxbox or Xfce over GNOME, but here in Debian, GNOME is running well enough that I'll probably use it quite a bit. I'll continue testing Fluxbox, but I imagine that GNOME will continue to be my main window manager on this box (as it has been when running off of a traditional hard drive).

It definitely depends on the specific box, and especially on the available RAM. I guess that 256 MB of RAM is enough for good GNOME performance. With 128 MB of RAM, Xfce, Fluxbox, Fvwm or other lightweight window managers might dramatically improve performance vs. GNOME.

One thing I have to do is run top when running the same apps in both GNOME and Fluxbox. If the same amount of swap, relatively speaking, is being used in both window managers, that tells me why my GNOME performance is so relatively good. But if there was a lot more swap used in GNOME vs. Fluxbox, then I'd know that the lighter-weight window managers are really making a difference.

This week's Tech Talk column covers the creation of what I call The Self-Reliant Thin Client, which is basically a very-bare-bones PC that is booting and running off of a Compact Flash module instead of a traditional spinning hard drive.

Here is the photo gallery, which will get full captions when I get the time to write them.

I have been wanting to test solid-state storage technology for some time now, and with the solid-state drive option for Mac laptops costing $600 (over and above the MacBook's $1,600 price), the drives themselves as laptop replacements in 64 GB sizes going for $170, I decided to use the slower but way cheaper Compact Flash technology, which is very common in high-end digital cameras.

I finally got an 8 GB Compact Flash chip from newegg.com for about $20, and I'm backing up my user files on a USB flash drive plugged into the back of the box.

The box — which started out as a Maxspeed Maxterm thin client — is running Debian Etch.

I know that the Opera Web browser is not a free, open-source application — which I almost always prefer — but the browser itself is a free download for Windows, Mac and in precompiled packages for many flavors of Linux as well as FreeBSD.

Question: Why another Web browser? While Windows and Mac users overwhelmingly use Internet Explorer and Firefox, with a smattering using Apple's Safari, there's plenty of room for other entries in the browser space.

I don't know about you, but I'm in a Web browser about 80 percent to 90 percent of the time, both for the traditional task of looking at Web pages but increasingly to use Web-based software.

And for something so important, choice is key.

Users of Linux and other Unix-like operating systems are used to having lots of browsers to choose from, among them Firefox (and its non-copyrighted Iceweasel offshoot in Debian), Epiphany (the GNOME browser created from Mozilla's Gecko engine), Konqueror (the KDE browser/file manager from which Apple took code to create Safari), Seamonkey (the Mozilla-created Web suite that's modeled after the now-dead Netscape Communicator, offering browsing, e-mail and Web design in one application), Dillo (a very lightweight browser), Netsurf (also lightweight), a few more that I'm probably forgetting, plus text-only browsers that include Elinks, Links, Lynx and W3m.

I'd never used Opera before, mostly because of its closed-source status, although I have been "forced" to use Internet Explorer -- also closed source (hey, it's Microsoft -- what do any of us expect?), and besides, IE runs only in Windows and not in Linux (without difficulty, meaning use of WINE or a virtual machine) or Apple's OS X.

And our main Web application insists on IE not for all, but for the most "advanced" operation.

Imagine my surprise a few weeks back when I saw staff artist and Flash guru Jon Gerung using the Opera browser for the very task that usually demands IE.

Since then, I've downloaded Opera and have begun using it to work on Dailynews.com -- and for everything else, too.

There are a few instances where the CSS drops out, one situation where a link won't open, but for 99 percent of my work on this task, Opera does it as good as IE, often times better -- and always much, much faster.

That's the best thing about the Opera Web browser -- it's very fast. And that matters a great deal when doing Web-intensive work. You want to wait as little as possible for the software to do its thing so you can ... do your thing.

The company that makes Opera -- called Opera Software -- provides versions for many platforms. It's a pity you can't get the source and compile it yourself for Linux/Unix, but the speed and functionality of Opera is too good for me to pass up at the moment.

I'll still use Firefox -- probably a lot -- since it's the go-to browser for just about everybody out there, and I need to use the Web Developer add-on, but there's no denying that Opera is simply one of the best applications I've seen lately.

In the battle for which operating system runs best on the $15 Laptop, Puppy Linux has pulled out front as the fastest system with the most features I need and best functionality on this 1999-era Compaq Armada 7770dmt.

In case you're wondering, here are the specs of the Compaq:

233 MHz Pentium II MMX processor
144 MB RAM
3 GB hard drive

I recently bumped the RAM from 64MB to the maximum of 144MB. Before this increase, running Linux or OpenBSD (which I have installed on the hard drive) with the X Window System was difficult at best.

Smaller applications like the Dillo Web browser, the Abiword and Ted word processors, the Geany and Beaver text editors ran pretty well in 64MB of RAM.

But the 500-pound gorilla of graphical applications is Firefox.

It would be nice to get by with Dillo, but many — if not most — of the things I need to do with a computer these days require a fairly modern browser.

Whether it's blogging, working on Dailynews.com, or on the Movable Type back end, it all happens in the browser.

And for that I need, at a minimum, Firefox 1.5.

Now that Damn Small Linux offers Firefox 2 (under the name Bon Echo, but for all intents and purposes an early release in the FF 2 series), that system is more than fair game for use on this laptop.

Unfortunately, while the browser runs great, other things in DSL have not been working so well.

For some reason, the desktop wallpaper doesn't work. Instead, I have a plain, gray X Window background. And while JWM (Joe's Window Manager) is the default in Damn Small Linux like in Puppy, switching over to Fluxbox in DSL has been problematic. Some builds have allowed me to use the Fluxbox menu, but others don't seem to work at all.

I could live without desktop wallpaper (or I could figure out a solution to the problem), but with Puppy Linux (I'm currently using version 2.13 but could easily upgrade to the newer 4.00 at any time) I get a nice-looking desktop, the Mozilla-based Seamonkey Web suite, Abiword (about as fast as DSL's Ted word processor but with the added ability to read and write .doc files), the Geany text editor, the ROX filer and quite a few other applications I've grown to like very much over the year and a half I've been using Linux.

And as far as speed goes, Puppy and DSL are quite equal on this hardware.

Coming up:

• In search of the best OS for a 9-year-old laptop: Part II — OpenBSD or Debian?
• In search of the best OS for a 9-year-old laptop: Part III — Browsers and wireless
• In search of the best OS for a 9-year-old laptop: Part IV — Wolvix Cub is surprisingly strong
• In search of the best OS for a 9-year-old laptop: Part V — Where I'm headed
• In search of the best OS for a 9-year-old laptop: Part VI — Younger Puppies
• In search of the best OS for a 9-year-old laptop: Part VII — Debian with Xfce and Fluxbox calls
• In search of the best OS for a 9-year-old laptop: Part VIII — Final thoughts (aka "Why?")

If you know the LAMP stack and want to live in Boston, the Obama campaign wants to hire you:

They need a programmer and a security expert.

That Obama ... in addition to being so gosh-darned dreamy, he embraces Linux and other free, open-source technologies.

How's John McCain gonna compete with that?

Related links:

• Technology Voters' Guide: Barack Obama
  
• Technology Voters' Guide: John McCain

Excerpts from the two guides above:

We have to know: what's your favorite gadget?

Obama: BlackBerry.
McCain: My slim, stylish gold Razr phone and I are inseparable.

And for the equal time's sake, here's a picture of John McCain back in the day:

For those of you who don't know, I've been writing a weekly tech column for the Los Angeles Daily News. It's usually available on the Technology page, where I've archived as many past columns as I've been able to find in the system.

This week's column is Stealing is still stealing. It's about the ethics of proprietary software. Is it OK to steal non-free software? How does free, open-source software factor into this ethical stew? It's nothing I haven't covered in this blog before, but it is a bit more up-to-the-minute as far as where I'm at goes:

Microsoft charges what it does because that's what the corporate market is willing to pay. And if the average guy sitting at home can pay hundreds of dollars for software, they'll take his money, too.

To a company like Microsoft, they'd prefer that home users steal its software and become familiar with it rather than use anything else. That way, when those same people go to work, they'll demand their bosses pay for the programs they know.

Red Hat has a Linux desktop plan. It's just a little difficult to figure out exactly what it is.

I think Red Hat knows this. And it's OK with it.

One day Red Hat bigwigs are saying that they are not interested in aggressively pursuing the Linux desktop market, that Ubuntu has much of it sewn up, and why do it anyway when all the money is in servers and the support Red Hat so richly provides to those who want it?

Good question.

But I see a strategy in there somewhere. Steven J. Vaughn-Nichols, late of Ziff Davis, now writing just about everywhere else, including his own Practical Technology, has met recently with a bunch of Red Hatters. In SJVN's recent post, the Red Hat people still push Fedora, the community distribution that serves as a testing ground for future Red Hat Enterprise Linux releases, but the company is sometimes not-so-quietly working on making its flagship RHEL product a better fit for the desktop — and laptops, too. And Red Hat does see a niche for RHEL apart from the server:

What Red Hat is working on is continuing to make RHEL (Red Hat Enterprise Linux) business desktop friendly. Whitehurst said many business customers want the Linux desktop. They don't want to move their desktops lock, stock, and barrel to RHEL, or any other Linux desktop. What Fortune 500 companies do want though is to start moving up to 25% of their desktops to Linux.

Why? Because they want the benefits of Linux. Besides the usual advantages of improved TCO (total cost of ownership) and improved security, Red Hat's corporate customers want a Linux desktop that can be carried as a virtual machine on a USB key and can be be managed by Red Hat's management tools. Is this for someone who wants a Windows XP Home replacement? No. It's not. It is, however, something that can catch the attention of CIOs who want a Windows XP Pro replacement.

And who can resist SJVN's money quote from Red Hat's Jim Whitehurst?:

"There are companies that sell hundreds of products for millions of dollars and there are companies that sell millions of products for hundreds of dollars. Guess which kind of company Red Hat is?"

It's a riddle, right?

OK, forget about all of that. Just read Red Hat's own press release for RHEL 5.2, which not only talks up all the work they're doing to make suspend/resume work but highlighting the inclusion of desktop applications that aren't a generation too old for office use. I'm talking about OpenOffice 2.3 and Firefox 3, the latter of which just had its final release this week.

Here are a few quotes from the RHEL 5.2 press release:

"We took part in the beta program of Red Hat Enterprise Linux 5.2," said William Cattey, Linux Platform Coodinator, MIT Information Services & Technology. "Re-basing the Red Hat Enterprise Linux desktop to have the latest Firefox, OpenOffice and Adobe Reader is very important to us because it gives our users the same key applications available on other platforms."

"LVM is very satisfied with our experience using Red Hat Enterprise Linux Desktop on the certified Lenovo T61 and X61 laptops," said Werner Schmidt, LVM's CIO. "We have deployed over 2,000 Lenovo laptops running Red Hat Enterprise Linux Desktop and plan to roll out several thousand more over the next several months."

The key in all of this is the corporate/enterprise connection, the idea not of wholly changing desktop platforms but bringing needed diversity to the desktop with Linux where appropriate, and leveraging the whole Red Hat relationship with server customers to solve problems on the desktop while adding incremental revenue and giving those customers even more reasons to stick with — and continue paying for — Red Hat.

And all those management tools, most of which I know nothing about, that Red Hat offers to keep servers in line and up to date — all that stuff can also make desktop management a more orderly procedure than the absolute mess that's going on now with Joe Worker's desktop PC.

Not that Ubuntu isn't also working on corporate, managed solutions for desktop PC management, but when it comes to paying for support, Ubuntu doesn't seem to be offering any deep discounts over what Red Hat is charging. And if a huge enterprise already has a lot of Red Hat on the premises, a little more doesn't hurt, right?

And there's another side to this valuable coin: While Ubuntu is mainly thought of as a desktop system, it's no secret at all that parent company Canonical is making a huge push into servers, with certifications coming for use on hardware from any number of vendors, commitments of long-term support and the same kind of sysadmin-helping tools that help leverage things for Red Hat.

So if Ubuntu is leveraging its desktop success to build a potentially lucrative server business, Red Hat needs to expand its own desktop commitment to keep and grow the already lucrative server market it currently dominates.

Who wins?

Damn near everybody, I figure. More competition means better products, most of which can be had for free. Remember, if you don't want to pay for Red Hat, there's always Fedora, or the RHEL clones put together by CentOS and Scientific Linux. And if you're deploying Ubuntu in an enterprise situation, you can pay Canonical, or leverage the substantial Ubuntu community to solve problems.

And while some of us can't imagine paying thousands of dollars a year for support on a server, that kind of thing starts to make sense in the enterprise when you weigh it with your own labor costs.

It's an equation that has worked in Red Hat's favor for a long time. And a few extra variables in said equation are just part of the game.

I had no idea that the Debian-derived apt and Synaptic are viable choices for package management in Red Hat Enterprise Linux and the free RHEL-like CentOS. Not that I have anything against RPM and Yum, but it's nice to have choices.

Dag Wieers shows you how on his blog, which I found via Planet CentOS. (Have you noticed that Planet CentOS is a great place to find out stuff?)

It's all courtesy of a project called APT-RPM.