Martin Pool's blog

Blosxom was ill

My blog was down for a while because I thought blosxom had broken — permalinks to articles didn't seem to work.

In fact, the only problem was that some of my articles about linux.conf.au had paths like /weblog/conf/lca/2005. It looks like paths with numeric components kick off Blosxom's heuristic for searching by date rather than by name.

This is some kind of lesson about not giving inputs too many magic meanings, I suppose.

Offline Blosxom-style blogging

A strength of systems like Blosxom and PyBlosxom is that they record all your entries as a tree of unix files, stored on the server.

So how do you record or edit entries when you're offline? One way is to store little files on a laptop, and then remember to upload them later. But this is a bit gross.

A better way is to use Unison to keep a mirror of your Blosxom document tree on your laptop. You can edit either end. When you're connected, resynchronize and it will help you resolve changes made to either end.

Blosxom Emacs Joy

Doug Alcorn had an emacs save-buffer-same-timestamp function, useful for editing Blosxom posts.

Backdating entries in Blosxom

Blosxom stores everything in Unix files, which is a nice simple system and makes it easy to edit. The date for each entry is just taken from the file's modification time.

The only catch is that any edited entries are moved forward to the current day.

Fortunately there is a good fix for this in the GNU touch -d command, which can set the file's time to any arbitrary point in the past or future.

The other thing I did was just put this line into the Blosxom configuration, because the noisehavoc host is not in Canberra (by a long way.)

$ENV{'TZ'} = 'Australia/Canberra';

first Blosxom post

This is my first Blosxom post.

Archives 2008: Apr Feb 2007: Jul May Feb Jan 2006: Dec Nov Oct Sep Aug Jul Jun Jan 2005: Sep Aug Jul Jun May Apr Mar Feb Jan 2004: Dec Nov Oct Sep Aug Jul Jun May Apr Mar Feb Jan 2003: Dec Nov Oct Sep Aug Jul Jun May