I make heavy use of vnet jails in FreeBSD at work. Due to FreeBSD's rc.d system not supporting vnet jails well, I opted to create a little command-line PHP project to make administration of jails easier. Though the tool was useful, it lacked in flexibility and usability. After learning how to write modules for Drupal, I opted to rewrite my jail administration project as a Drupal module. Though I wouldn't recommend running this project in a production environment, it's very useful for development environments. I use different jails to keep different development projects organized.

For the past month, I've been working on fixing just a single bug in the FreeBSD port of libhijack. I finally fixed the bug last night! We're getting closer to a new release of libhijack, which will support 32bit and 64bit Linux and 64bit FreeBSD. I'm going to leave out 32bit support on FreeBSD simply because no one uses 32bit FreeBSD anymore. If anyone would like to add 32bit FreeBSD support, I'll gladly accept patches (assuming the code looks good). There's still at least a month's work left to do.

What's left to do:

I blogged yesterday about the Solaris 11 source code leaking and encrypted ZFS pools in FreeBSD. This little tech blog generally gets around 20-40 hits per day. Yesterday saw nearly 4,000 hits. Today has so far logged around 2,000 more. My G+ post says it all. I can't believe my server was able to survive so many hits. I did a good job in setting it up.

ZFS introduced encrypted datasets in zpool verison 30, which is only available in Solaris. FreeBSD and IllumOS use zpool version 28. For FreeBSD users, encrypted ZFS is still a possibility and is rather easy to do (I'm sure it is on IllumOS as well, I just haven't learned how to do it). In this article, we'll step through how to create an encrypted ZFS pool in FreeBSD.