The printer is a HL-2170w which has a quaint Web interface for configuring it, but works great with the Mac. You can’t really see the SUA1000XL which is the most awesome UPS I’ve ever been able to hold off the ground without help. It’s around 55 pounds and able to run the whole setup for 39 minutes (something on the order of 38% load, when I leave and the monitors powersave it goes down to 10% load and around 90 minutes runtime). Behind the printer is the D-Link gigabit switch which works great and supports jumbo frames, and next to it (also not visible) is the first photo backup drive (HFS+, covered in a couple of paragraphs) and two external ReiserFS data drives. Of course the printer is not on a UPS, since it draws too much on startup (the main UPSes actually kick on because the line voltage drops too much at that point, since I only have one circuit to my bedroom).

The backup scheme I use for photos is pretty solid, I think. Coming out of the camera, I keep the photos on the flash card until they’re backed up fully in Texas, at which point I mark the card as erasable. The last couple of months stay on my laptop, and everything before that is then on the external hard drive and in Texas, on a machine named Toothpaste (simply for the sheer joy of asking people “Where’s Toothpaste?” in everyday conversation). Yearly it also gets burned to DVD and the DVDs are kept in a box with the expectation that I’ll never have to use them. Toothpaste is a lowly Celeron 566 which is optimized to the hilt for low power consumption (around 25w idle, 45w with all disks spun up and transferring large amounts of data).

Astute readers who spend as much time at Ikea as I do might recognize the Galant desk surface and Vika Fagerlid legs. I actually got the desk surface first from the as-is area and decided on the legs later (as I was running short of shelf space). What you can’t see is that there is another, different leg at the back corner which is from another series which is 3/4” shorter than the others. The solution was pretty simple, cut a piece of 1 × 4 and screwed it on (this probably qualifies me for a post on Ikea Hacker, since “cut the allen wrench and use in a drill” made it into a post last month).

This doesn’t seem to be officially exposed anywhere on the Leopard client, but I can find references to a collaboration server by searching online. Strange.

• Download PIL 1.1.6 source package and have the Developer Tools already installed
• Patch setup.py with this patch so it can find the Freetype you already have. (patch -p0 < leopard_freetype2.diff)
• sudo apt-get install libjpeg if you have fink (otherwise, build by hand and adjust paths)

You can use it without jpeg support but im.show() has jpeg hardcoded as the filetype so you would need to work around that.

Berto thought it necessary to combine two of my peeves (perl and Comic Sans MS) into one image and send it to me in an innocuous name like “Picture 1.png” in Skype. I closed it as soon as possible, but it just haunted me from the Leopard Dock when I returned from lunch.

Typically this means that an extension was compiled against the wrong Python.h.

This just means that the calling Python interpreter and the extension don't use the same version (one is Python 2.4, the other 2.5). They were both 64-bit but the name changed in http://www.python.org/dev/peps/pep-0353/

Some commands to help debug this are ldd (to show dymanic library linking) and nm (to list exports).

       *   $PUSH1
       |\
       | * 
       |  \
       |   * $PUSH1
MERGE1 *--/ \
       |     \
       |\     * $CUR2, I don't want this.
       | \
       |  * $PUSH2, I want this, so I can...
MERGE2 *-/

Here’s how:

Background

I pushed $PUSH1, which got merged with $TRUNK, creating $MERGE1.

Some local changes (on top of $PUSH1) later, I am ready to push again (I have $CUR2 and want to end up with $PUSH2 on top of $MERGE1).

First, enable the transplant extension.

[extensions]
transplant=

Go ahead and pull so you have multiple heads in your local repo (don’t push to your personal remote, any of ($MERGE1:$CUR2] or you’ll have to go through an extra set of steps first, below).

Rebasing in HG

# we start with two heads, $MERGE and $CUR2, and no uncommitted changes
hg update -C $MERGE
hg transplant --branch $CUR2
# at this point, your $MERGE head is updated to what we'll call $MERGE2
cd ..

# this is the easiest way to remove $CUR2's head
hg clone -r $MERGE2 repo new_repo
mv repo old_repo
mv new_repo repo
cd repo
hg push

Extra steps if you pushed

If you did push something on $CUR2’s line, you’ll need to fix that first.

ssh remote

hg clone -r$MERGE1 remote new_remote
cp remote/.hg/hgrc new_remote/.hg/
# set permissions like they were before
mv remote old_remote
mv new_remote remote