Thanks to Hurricane Electric’s IPv6 Tunnel Broker, setting up these IPv6 networks was fairly painless. The only real exception here was in my dorm room, as our residential network filters inbound ICMP (inbound anything from the public net really) and prevents Hurricane Electric from allowing a tunnel to be created. To work around that, i’m using 6to4 on my DD-WRT powered WRT310N. The DD-WRT docs have a decent writeup on 6to4 available here.

A bit of Python polls owserver using a SWIG module and commits the read temperature value to a MySQL database. I munged some of Mikal’s graph server code to simply post the chartserver URL to appengine so it could be hosted for the world to see.

QMMP with Winamp base skin

The classic skin came from here. Just download the .zip and place it in ~/.qmmp/skins, open up the settings, make the switch, and you’re good to go.

The code is something like:

self.cups = cups.Connection()

def getActualPrinter(self, jobid):
job_attributes = self.cups.getJobAttributes(jobid)
return job_attributes['job-actual-printer-uri']


Now with the added code, I’ve added physical destination to the CCIS print queue viewer. We have several queues that all point to the same printer (name-simplex, name-duplex, etc all point to name). The same code for identifying destination on print classes also works for these cases.

CCIS Print Queue Viewer

If one creates a print class in CUPS, is it possible to query for the destination printer within that class that a job was actually sent to? There seems to be very little documentation on this sort of thing…

A quick how-to install is included below.

$ sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys E5C2D9CD
$ sudo sh -c 'echo "deb http://ppa.launchpad.net/compbrain/ppa/ubuntu jaunty main" > /etc/apt/sources.list.d/compbrainppa.list'
$ sudo apt-get update && sudo apt-get install python-gflags


$ mencoder -forceidx input.avi -o output.avi -oac copy -ovc copy
$ mv output.avi input.avi


After that, the new input.avi should be playable, and seeking should work properly again.

Since the primary purpose of the server in question is to handle e-mail, no webserver was installed. After stumbling upon http://aleksandarsavic.com/nginx-redirect-wwwexamplecom-requests-to-examplecom-or-vice-versa/ I whipped up a 6 line config for nginx, and deployed it on the machine. nginx is lightweight enough to be installed specifically for this purpose without making a drastic impact on the machines other tasks.

Here is our config:
## Redirector for ccs.neu.edu
server {
listen 80;
server_name ccs.neu.edu;
access_log /var/log/nginx/access.log;
rewrite ^(.*) http://www.ccs.neu.edu$1 permanent;
}