I'd much rather use Git over Subversion, but I still have one project (leaguerunner) using Subversion on Google Code. Migrating the code itself to git is fairly simple, but being unable to migrate the issues still needs some tool development.

more

You may have heard that WIND Mobile is going to be offering service in Ottawa shortly. I got curious as to what their coverage might be and started looking for coverage maps. I didn't find any, but I ended up graphing their wireless backbone instead.

more

A while back, I posted about detecting virtualization on Linux from a shell, using various tricks. Around that time, I also implemented those tricks as a perl script for internal use at work with the intent of eventually cleaning it up for public consumption. I finally got around to doing it, and the result is Sys::Detect::Virtualization availabe from CPAN, or from GitHub.

Currently, it can only handle Linux, and is only tested on a small number of virtualization hosts. Patches are welcome.

Today, my Thinkpad T61 decided to stop working. While I was in the middle of reading email, it just stopped. Completely blacked out -- no AC light, no battery light, nothing. Here's how I got it working again.

more

I recently moved our automated testing systems from a KVM+Qemu setup to Linux-VServer. We didn't need the overhead of a full virtual environment, even one as lightweight as KVM. However, there was a little snag -- 127.0.0.1 didn't work correctly.

more

Until today, this blog ran on vimblog, a hand-rolled minimal script for displaying blog entries. In the last year or so, though, I've become a convert to git, and so what I really want to do is edit my posts on any system, commit them to a git repository, push to a remote and have them end up as blog entries on my server. Fixing vimblog to do this would have been more work than I want to deal with, but thankfully ikiwiki exists, and can do most of what I need.

So, as of now, this blog is in ikiwiki. To get there, I followed (more or less, since I'm documenting after-the-fact) these steps:

more

At my job we have need of a high-performance hash lookup database in our antispam product. It's used to store Bayes tokens for quick lookups on individual scanning systems, and is read-only in the fast path (mail scanning) with updates taking place in another process. For the last few years, we've been using a plain old BerkeleyDB hash database via Perl's DB_File, but with all the hype about Tokyo Cabinet and its benchmark results I figured it was time to take a look.

more

A while ago, I blogged the chrooting of bind9 on Debian, so I wouldn't forget how to do it. Things have changed slightly for Lenny, so here's the update.

more

I recently came across a Vim tip explaining how to display shell commands in a different buffer. While useful, it opens a separate scratch buffer every time you run the command. I wanted to make it reuse the same scratch buffer, so that whenever I ran my unit tests using it, they overwrote the previous run's output. As it turns out, Vim has a way to do this.

more

ack is a great "programmer's grep" tool. If you don't already use it, check it out. Now, ack is packaged as part of Debian Testing (Lenny), but unfortunately there's a name conflict. Debian already ships a Kanji code converter named ack, so the ack that I want gets renamed to ack-grep.

I want to run 'ack' on all my systems, not 'ack' on some and 'ack-grep' on others, so I abused Debian's 'alternatives' system to let me do this with:

    update-alternatives --install ack ack /usr/bin/ack-grep 100

And voila, it creates me a /usr/bin/ack that Just Works, and is known to Debian so future packages won't (I hope) break that symlink.