In search of the best OS for a 9-year-old laptop: Part I — Puppy or Damn Small Linux

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?”)

OpenBSD: the fvwm man page does not reveal all, but I have a workaround, plus more on OpenBSD

Yesterday I went on about the man page for fvwm, the default X window manager in OpenBSD.

It clearly says that, in the absence of a .fvwmrc file in the user’s home directory, fvwm will look in /usr/X11R6/lib/X11/fvwm/ for a file called system.fvwmrc:

During initialization, fvwm will search for a configuration file which describes key and button bindings, and a few other things. The format of these files will be described later. First, fvwm will search for a file named .fvwmrc in the user’s home directory, then in ${sysconfdir} (typically /usr/X11R6/lib/X11/fvwm). Failing that, it will look for system.fvwmrc in ${sysconfdir} for system-wide defaults. If that file is not found, fvwm will be basically useless.

There’s a file called system.fvwm2rc in that directory, but it doesn’t control fvwm. I know this because I added a line to it, stopped X and restarted it. No change.

Since fvwm looks for the .fvwmrc file in the user’s home directory, I decided to create one with the help of the system.fvwm2rc file mentioned in the man page.

I used the Geany editor, but substitute any text editor you wish (I’m just more comfortable in a GUI editor when it comes to things like copying and pasting. I don’t use vi enough to be all that proficient).

Here’s how to do it:

Log on with your user account, open an xterm window and do the following (again, substitute your favorite editor for geany, or install the geany package on your OpenBSD system with $ sudo pkg_add -i geany):

$ geany /usr/X11R6/lib/X11/fvwm/system.fvwm2rc

Under the File menu in Geany, choose Save As, then navigate to your home directory and save the file as .fvwmrc (in other words, create /home/~/.fvwmrc, substituting the name of your user’s home file for ~)

Now you should have a .fvwmrc file in your home directory that is editable by the user account. Modifying the menus is pretty easy. I’ve already added a category for applications and added all the apps I’ve installed thus far to it.

I’d still love to find out where the systemwide fvwm configuration file really lives. I don’t have enough Unix or OpenBSD knowledge to do so at this point.

I’ve stuck with fvwm because it’s the default window manager in OpenBSD, and it’s pretty nice once you learn about it. I’ve got a long way to go, that’s for sure.

Fvwm note: Changes in your .fvwmrc aren’t implemented until you quit X and restart it.

Applications I’ve added to my OpenBSD box thus far:

Geany (text editor)
Dillo (lightweight GUI browser)
Firefox (heavyweight GUI browser)
Nano (console text editor; I just “get it” more than vi)
MC (console file manager)
Rox (the ROX-filer GUI file manager)
Abiword (relatively lightweight word processor)
Ted (even lighter RTF-format word processor)

I haven’t added a mail client, and I might add Sylpheed or Thunderbird. I might also add mutt, fetchmail and msmtp and try POP mail from the command line for one account. Generally, though, the whole console e-mail thing baffles me — and yes, I have done it before. I generally find a GUI mail client or Web mail interface so much easier that I don’t need to spend days and days fiddling with mutt.

Essential OpenBSD reading: The OpenBSD Journal. I just found out about this, although I’m sure I’ve been here before.

Also: OpenBSD 101.

Ted on OpenBSD: I installed the Ted word processor — an exceedingly light application that reads and produces files in rich text format — which can be read and edited by most word-processing applications, including Microsoft Word.

Ted on OpenBSD … how to actually run it:

This doesn’t work:

$ ted

But this does:

$ Ted

Remember, Unix-like OSes are case sensitive, and in the case of Ted, it’s really capital T, small e, small d.

I’ve been grumbling about Ted not working in Debian for an age, but Ted works fine in OpenBSD. I’ll probably use Geany for most of my work, though. I got used to Geany by using it in Puppy Linux, and while I’m not crazy about its Windows implementation, in Linux/Unix, I still really like it.

Debian Lenny, the Ted RTF word processor, and the fate of the $15 Laptop

I’ve complained numerous times in the past about the Ted word processor being broken in Debian. On my many Debian installs, I could neither create a new file in Ted nor open an old one.

But on my Gateway Solo 1450 (the $0 Laptop), after doing my big Debian Lenny update yesterday — which fixed an annoying Nautilus bug by updating to Nautilus 2.20 — I decided to give Ted another try.

It works.

I can create new files in Ted and open old ones. I tried Ted again on my Compaq Armada 7700dmt (the $15 Laptop), now a Debian Etch machine (with Xfce and, since last night, Fluxbox) that could really benefit from Ted working. No go.

I figured that it was maybe a Lenny-only thing — some other dependent package got updated and magically made Ted work. Here’s Ted’s bug status in Debian. I remember trying this “transcoded fonts” solution and having it not work.

So this morning, on my desktop Debian Lenny install, I tried Ted again, and it didn’t work. I even installed the transcoded fonts. Nothing.

Yes, I have three Debian installs (two Lenny, one Etch), and Ted works on one (Lenny) of them. That’s better than Ted working on none … but.

I’m wondering if I should even be running Debian on this 233 MHz Pentium II MMX, 64 MB RAM, 3 GB hard-drive laptop. The Compaq performs OK with Puppy Linux and a bit better with Damn Small Linux. And while on my faster, 1.2 GHz laptop I detect almost no difference in response time between Xfce and Fluxbox, on the 233 MHz box, Fluxbox is much snappier, so I take back my previous assertion that Fluxbox doesn’t give you much of a performance edge. When you’re running really old hardware, Fluxbox can really help.

The problem: I want to have a “full” command-line system in addition to X, and that’s harder to do in Puppy or DSL. And I like the fact that Debian and Slackware stay on top of security issues and frequently issue patched packages. And Debian (or Slackware, for that matter) makes it relatively easy to install any console app I want. However, I put a lot of stock in doing as little modification as possible; in my experience, things can get mucked up pretty quickly. And while both Puppy and DSL offer command-line features, neither is a full, modern, updated Debian or Slackware.

And just to provide a little background, Debian, Slackware, Puppy and Damn Small installed just fine on this old Compaq. I can’t say the same for Xubuntu, which I did try.

And while I’m mentioning Xubuntu and Debian with Xfce in the same post, let me just say that of the two, Xubuntu is way more ready for prime time. Debian’s default Xfce install is missing too many things; I stick by my assertion that Debian is great with the default GNOME, less so in the Xfce and KDE installs that you can do with the Xfce and KDE Debian disks (or desktop= boot parameter in the netinstaller).

Back to the Compaq. Both Puppy and DSL are way better at recognizing and configuring the hardware of this old Compaq laptop. At this point, I’m considering running both Puppy and DSL as live CDs with no OS on the puny hard drive, which would only be used for swap and storage (I could even replace the spinning hard drive with a Compact Flash chip or disk-on-module).

I hate to give up running Debian or Slackware on this laptop — I’ve tried both. But when I try to build up the apps on my own, I can never do as well as Puppy and Damn Small Linux — both of which I’ve used extensively over the past year and which I value very highly. The people behind Puppy and DSL really know what they’re doing.

And while I’m grateful to get Ted running on my Lenny laptop (where I don’t really need it), can’t Debian just make Ted work everywhere, all the time? Like I’ve said before, there’s probably a good reason that Ubuntu doesn’t have Ted in its repository, and I’d say the package not working is a pretty good reason.

I haven’t even complained about Ted not showing up where it should in the menus and my not being able to figure out how to put Ted where I want it in GNOME (yes, I used alacarte (here’s the Debian bug situation), and no, it didn’t let me add menu items (another Lenny bug, perhaps?) — it almost makes me want to run straight toward Xfce and Fluxbox … or Ubuntu).

Moral: Debian giveth and taketh away, but it remains damn good.

Debian Lenny, the Ted RTF word processor, and the fate of the $15 Laptop

I’ve complained numerous times in the past about the Ted word processor being broken in Debian. On my many Debian installs, I could neither create a new file in Ted nor open an old one.

But on my Gateway Solo 1450 (the $0 Laptop), after doing my big Debian Lenny update yesterday — which fixed an annoying Nautilus bug by updating to Nautilus 2.20 — I decided to give Ted another try.

It works.

I can create new files in Ted and open old ones. I tried Ted again on my Compaq Armada 7700dmt (the $15 Laptop), now a Debian Etch machine (with Xfce and, since last night, Fluxbox) that could really benefit from Ted working. No go.

I figured that it was maybe a Lenny-only thing — some other dependent package got updated and magically made Ted work. Here’s Ted’s bug status in Debian. I remember trying this “transcoded fonts” solution and having it not work.

So this morning, on my desktop Debian Lenny install, I tried Ted again, and it didn’t work. I even installed the transcoded fonts. Nothing.

Yes, I have three Debian installs (two Lenny, one Etch), and Ted works on one (Lenny) of them. That’s better than Ted working on none … but.

I’m wondering if I should even be running Debian on this 233 MHz Pentium II MMX, 64 MB RAM, 3 GB hard-drive laptop. The Compaq performs OK with Puppy Linux and a bit better with Damn Small Linux. And while on my faster, 1.2 GHz laptop I detect almost no difference in response time between Xfce and Fluxbox, on the 233 MHz box, Fluxbox is much snappier, so I take back my previous assertion that Fluxbox doesn’t give you much of a performance edge. When you’re running really old hardware, Fluxbox can really help.

The problem: I want to have a “full” command-line system in addition to X, and that’s harder to do in Puppy or DSL. And I like the fact that Debian and Slackware stay on top of security issues and frequently issue patched packages. And Debian (or Slackware, for that matter) makes it relatively easy to install any console app I want. However, I put a lot of stock in doing as little modification as possible; in my experience, things can get mucked up pretty quickly. And while both Puppy and DSL offer command-line features, neither is a full, modern, updated Debian or Slackware.

And just to provide a little background, Debian, Slackware, Puppy and Damn Small installed just fine on this old Compaq. I can’t say the same for Xubuntu, which I did try.

And while I’m mentioning Xubuntu and Debian with Xfce in the same post, let me just say that of the two, Xubuntu is way more ready for prime time. Debian’s default Xfce install is missing too many things; I stick by my assertion that Debian is great with the default GNOME, less so in the Xfce and KDE installs that you can do with the Xfce and KDE Debian disks (or desktop= boot parameter in the netinstaller).

Back to the Compaq. Both Puppy and DSL are way better at recognizing and configuring the hardware of this old Compaq laptop. At this point, I’m considering running both Puppy and DSL as live CDs with no OS on the puny hard drive, which would only be used for swap and storage (I could even replace the spinning hard drive with a Compact Flash chip or disk-on-module).

I hate to give up running Debian or Slackware on this laptop — I’ve tried both. But when I try to build up the apps on my own, I can never do as well as Puppy and Damn Small Linux — both of which I’ve used extensively over the past year and which I value very highly. The people behind Puppy and DSL really know what they’re doing.

And while I’m grateful to get Ted running on my Lenny laptop (where I don’t really need it), can’t Debian just make Ted work everywhere, all the time? Like I’ve said before, there’s probably a good reason that Ubuntu doesn’t have Ted in its repository, and I’d say the package not working is a pretty good reason.

I haven’t even complained about Ted not showing up where it should in the menus and my not being able to figure out how to put Ted where I want it in GNOME (yes, I used alacarte (here’s the Debian bug situation), and no, it didn’t let me add menu items (another Lenny bug, perhaps?) — it almost makes me want to run straight toward Xfce and Fluxbox … or Ubuntu).

Moral: Debian giveth and taketh away, but it remains damn good.