I last checked the NetBSD Project's website a few months ago and their design was more or less the same in May as it was 7 years ago. I just went back today and it looks like after 7 years they finally got a face-lift.

I have a lot of love and respect for BSDs, including OpenBSD and its great to see that they've only had two (discovered) remote holes in over a decade. However, this second vulnerability raises some questions as to their code auditing process. Consider how this hole has existed in the kernel sources for quite some time (at least version 3.1, released in 2002). It makes me wonder whether the OpenBSD team has gotten complacent and began slacking or whether they lack the personnel/time to really audit their source tree. I'm not criticizing anyone, but it just makes me wonder how a team that's supposedly so proactive on security issues overlooked this vulnerability, which in their kernel for so long.

I wrote a quick how-to on setting up FreeBSD as a wireless access point (router). I have the How-To and configuration files available here and have gotten this How-To published at HowTo Forge.

Despite its age and all the updates to it, there still appears to be no tool for shrinking a UFS/FFS partition. It can be grown, but not shrunk. I'm wondering if this is because no one has bothered to write such a tool or whether it's a technical limitation.

I filed a bug report and I got a patch within hours. How schweet is that?

A FreeBSD powered Sun Blade is now my Wireless Access Point using an Atheros-based PCI card for handling the 802.11b/g traffic.

Update 21 March 2007: I had a how-to on this published at HowtoForge.

Reasons I love FreeBSD: ports, support for 3 packet filters plus QoS and GELI-based disk encryption.

I now have OpenBSD installed on my Sun Blade.