What I'm Thinking About

Monthly Archives: October 2009

Shortly after Obama took office, his administration launched the “Recovery.gov” website. I found it notable that it was built on Drupal, an open source community content management system, on a short schedule and small budget.

When I posted about it, quoted a Reddit commentator who claimed to have been involved in its implementation. In addition to providing information about the schedule and budget for the site, he said they were currently engaged in trying to move the Whitehouse.gov website from a microsoft-based system that was developed under a $20M outside contract, over to Drupal or some other open-source framework, like Django, or Rails. Well, this week we learned how that turned out.

Drupal was started in 2000 as a discussion board and news site for Dreis Buytaert’s dorm. The Howard Dean campaign commissioned improvements to underpin their strong social media strategy. That work lead to Drupal’s use by a lot of political and social organizers, including the Obama campaign.

I continue to think that the story of how Drupal went from a college dorm to the Whitehouse in less than a decade is an interesting thread connecting a much lager story:

It should provide a great lens for examining the rise of OpenSource software post the dotcom crash, the blossoming of social software, the evolution of political organizing and fundraising in the Internet-era, the role of agile development in government IT, and the role of the Internet in reshaping and opening government. Plus, it started in a dorm, so I’m sure there is some sex, drugs, and rock and roll in there too.

If those things don’t fascinate you, what the hell are you doing reading Geekfun?

When WordPress.com launched themes targeted at small screens like the iPhone earlier this week, I was reminded that I was going to figure out how to improve the way Geekfun and our other blogs like Pet Project look on mobile devices. Long ago I tried an early iPhone theme for WordPress, but gave up on it, I think because it created problems with the caching solution I was trying to use at the time.

This time out, the solution was simple. I installed the sweet WPTouch plugin from Brave New Code. I’m quite happy with it. It loads quickly and it is very readable and easy to use. It only displays for mobile users, everyone else still sees your blog’s original theme, and its easy for Mobile users to switch to your regular theme if that is what they prefer. It is also allows for a healthy amount of customization, which I’ll have to dive into deeper before rolling it out on our other sites.

As of Ubuntu 9.04 (aka Jaunty Jackelope), it is no longer necessary to jump through hoops to access files on an Ubuntu (or Debian) server from a Macintosh OS X client via netatalk. Unfortunately, if you’ve previously gone to the trouble of jumping through those hoops by doing a custom compile of netatalk with openssl support , you are likely to run in to problems once you upgrade to Jaunty (and probably the soon to be released v9.10, aka Karmic Koala). Fortunately, the fixes are pretty easy if you’ve managed to find this blog post.

There are two issues. First, in order to support encrypted login, the custom build and configuration of netatalk loads some custom user authentication managers (‘uams’) that aren’t present in the latest packaged version of netatalk. The /etc/netatalk/afpd.conf file probably ends with a line like this:

This both produces failures when trying to load the nonexistent modules, it also means the default modules fail to load, including a new, prebuilt, module ‘uams_dhx2.so’ which supports encrypted authentication on Mac OS X 10.4 and later. The simplest solution is to edit /etc/netatalk/afpd.conf to either remove or comment out that line and just use the defaults. Once you’ve updated the config, restart netatalk with the following command ‘sudo /etc/init.d/netatalk restart’.

The next problem is that the newer versions of netatalk use a newer version of a simple database library to store Apple-specific file information. They provide a script for updating the db files, but you probably don’t know to look for it to run it manually. For details, check the README.debian for the netatalk package, which is most likely found in ‘/usr/share/doc/netatalk/README.debian’.

Upgrading Problems
==================
This version of Netatalk use to Berkeley DB 4.7.

Earlier releases used Berkeley DB 4.2. As Netatalk does not
automatically update its database, you may experience problems like
those described in bug #200373: no files showing up in your folders.

If you have such problems, you may try to upgrade the database using the
script /usr/share/doc/netatalk/examples/netatalk_update.sh
[…]

Before you run the script, run ls -la on the target directory and pay attention to the user and group ownership on the .AppleDB directory because after running the script, it tells you to check the permissions/owernership on the files it updated, and it is really good to know what the correct permissions were.