Since my blog is still fairly new, it’s a little bit in flux. I’ve moved Debian from / to /tech, and trying to put some non-Debian tech pieces in there. Thanks to Apache’s nice RedirectMatch support, it was just one line in a .htaccess file. I’m not sure if that’ll scale if I continue moving stuff around, but I hope so. I am of the firm belief that URLs which are published and not clearly temporary (includes /tmp or /temporary or something) should be valid for as long as possible, even when it’s painful to maintain it.

I think I need some better formatter for pybloxsom; writing HTML isn’t my style, but the wikiparser sucks. I guess I’ll take a look at the other offerings before I’ll look at writing my own. I’m trying to structure myself a little bit and possibly make pyblosxom into something of a personal portal or something, but also interesting and usable for other people. Not sure how it’ll work out, but I’ll give it a shot.

The genericwiki module in pybloxsom sucks. It doesn’t have bulleted lists, for instance, and adding them is not something which I feel like doing at this time of the day. I should probably just sit down and write my own wikiparser, probably based off the CVSWiki parser, which I find mostly sane (not so surprising, since it’s made by my friend Sesse, who mostly makes sane or at least non-insane software. Apart from stuff like adding an IRC frontend to my mailing list manager and such, that is.).

It’d be nice to have smileys replaced with some image tags and such also. Another day, I guess.

Tor Henning fixed up iota; the problem was related to some people not having any mail addresses. This caused InnovisionBoard to freak out, it seems. So, removed that issue, at least, even though it’s not I who have done it.

this is kinda cool, if you take a look at my blog, you’ll see the todo list at the right side. This is just hacked together from the booklist (which I also fixed so that I can have different book lists in different categories). I think I like pyblosxom. As soon as the code is cleaned up a little bit, I’ll post it.

#parser textile I’m considering the following list of benchmarks:

• price guide update
• lame/oggenc
• mencoder/transcode
• apachebench
• spamassassin, sa-learn
• Mersenne primes

Those should make the system churn a bit, and also be typical of some things you’ll actually do with a system, in production. Will be fun.

When out biking today, I thought of a few programs which would be immensely useful (and not so much):

• thought recorder. How often haven’t you had a brilliant idea or something you must remember, but once you get somewhere you’ll be able to write it down, you’ve forgotten?
• a good bandwidth shaper. I want to be able to: throttle one flow (one of my connections might be an rsync over ssh. That does not mean you should throttle all my other ssh connections as well) and throttle one “class” (say, throttle all HTTP traffic)

Of course, this list is missing at least five items, because I don’t have the first item. And, as an added bonus, I’ve begun thinking in English instead of Norwegian for the last day or so. Annoying, but I guess it’ll pass once I’m back at the university or something.

The problem with the 32bit glibc on 64bit AMD64 can be worked around fairly easily. The problem seems somehow connected to the optimized libraries placed in /lib/tls. The workaround is to just move /lib/tls out of the way, and hey presto: glibc works again. Of course, this is just a workaround, but it’ll do for now. I’ll give the lib64c6 some attention and upload it to Alioth once Alioth is back on line.

I have my $HOME in CVS, as joeyh has described on anoncvs-over-cvs and cvshomedir. I also check it out onto the web. Quite nice and convenient. Now I’ve also gotten the weblogging software set up; quite ok once Oskuro told me about the fact that the version in unstable is old and broken, and that there is a newer version in experimental.

I think I might want some better way of autolinking stuff I’m writing, but so far, I’m sticking with the plain frontend.

You just love it when you have a spare system that you might be able to use to build glibc and it just dies? Nice MP2600+, dual CPU and everything. splat. Dead. No reaction from ping, nothing. It sucks.

ok, got the amd64 to build, using a fairly ok-ish patch. Problem with 32 bit libc6 and amd64 seems to be related to the ds1 repackaging (and resyncing with upstream CVS). The joy of trying to wade through a 89k line patch trying to pinpoint what the problem is.