Category Archives: Uncategorized

Installing nodejs from source on Debian

This post is a snip from


Node.js is available in official repo for Debian Sid(unstable).

For Debian Wheezy, you have two options:

Build from source

sudo apt-get install python g++ make checkinstall
mkdir ~/src && cd $_
wget -N
tar xzvf node-latest.tar.gz && cd node-v*
sudo checkinstall -y --install=no --pkgversion 0.10.24  # Replace with current version number.
sudo dpkg -i node_*


sudo dpkg -r node

Restrictions on domain names used with Google Apps

I’ve been wanting to move to Google Apps for a while now but never really had the time to do it. Tonight I decided to spend the 20 minutes or so it would take to create the account and move the MX record and load my old mail via IMAP.

It turns out that Google has some restrictions on domain names that they will allow to be used with Google Apps. This list was taken from their signup restrictions page.

  • Domain availability in our system
  • Inappropriate domain names (offensive, false branding, etc.)
  • Restricted locations
  • Number of domains that you have already registered (this is meant to prevent abuse of our system)
  • Involvement in IT decisions for your organization

It seems falls into one of those categories, I’m guessing the one that I’ve bolded. I took a guess that Google doesn’t like the word stupid. A quick search for google apps restrictions domain name stupid shows that my guess was correct. I’m not the first person to have a problem with Google’s seemingly arbitrary domain name filtering.  This guy has run into the same problem I did but unlike me he had a friend at Google to get in touch with to help him out.

I’m hoping someone from Google stumbles across this and will get in touch with me and help me work this out. I plan on mashing buttons on the Google Apps site with hopes of finding a contact form that will allow me to get in touch with Google and have an exception made for

Easy access to the HTML Devel::Cover report from Dist::Zilla::App::Command::cover

I love me some Dist::Zilla and Dist::Zilla::App::Command::cover. I wanted an easy way to load the Devel::Cover HTML coverage report. I’ve been using this on my Macbook.

dzil cover | grep ‘coverage.html’ | awk {‘print $5’}  | xargs open

and this on Ubuntu.

dzil cover | grep ‘coverage.html’ | awk {‘print $5’}  | xargs -I{} firefox {} &

Kindle, usbNetwork and You

My Kindle shipped with firmware 3.0.2. I wanted to upgrade to 3.1 to get real page numbers. When I got the Kindle I jailbroke it, installed usbNetwork and the screensaver hack.

Every time I tried to upgrade the firmware it would fail. After some searching I found that the firmware updates ship with differential updates. If any of the core files are modified the update will fail in order to prevent mucking something up.

An easy way to figure out what file is causing the upgrade to fail is:


You can then search through the file created on the Kindle for the file with a checksum failure.

In my case /etc/sysconfig/iptables was modified. Someone posted a stock copy of the file, once I removed the the single line that was different in mine the update applied without issue.