At work, finished setting up the new Cornell computer (I think) and started figuring out how to set things up so everyone can run a ZEO server on their development machines, instead of directly using FileStorage. As an amusement, I reformatted my /data partition to use Reiserfs instead of ext2, since I'd like to get some experience with it. My /data partition holds various large source trees that are mostly external, and that I just CVS update, compile, and perhaps install: Mozilla, KDE, Linux, and the Python 2.0 CVS tree. As an experiment, I started up a KDE compilation with "make -j 2" and then turned the computer off, since Reiserfs is supposed to handle such crashes better than ext2 does. The results weren't encouraging; the machine rebooted OK, and the kernel logged a "Replaying 5 transactions" message when the partition was mounted, but then some files, such as the "configure" script, "config.cache", and "Makefile" were replaced with binary junk, perhaps from one of the object files being produced at the time of the crash. Maybe there's something I don't understand about setting up Reiserfs, perhaps some startup script or fsck invocation needed to reconcile matters.
splork: The un-SWIGged BerkeleyDB module is here. I'm still not very confident in it because I don't have a comprehensive test suite for it. Jim Fulton also pointed out a few missing API functions that need to be added, so I hope to hack on the module again before too long.
My previous Advogato diary entry was on August 31; it's much easier for me to maintain my personal diary pages, since I can let an entry slip for a few days and still get the date right, so readers interested in my diary should follow those pages.