This is the 200th post here – neat! I’m averaging just under 1.5 posts per day, which is good: healthy posting, healthy project.
I haven’t had any posts for the past day or so because there’s not been a lot of activity on the mailing lists, and I’m working up an ‘end-of-year’ report similar to the FreeBSD Status Reports. No link yet, cause it’s not done.
I’ve corrected my how-to-install writeup, based on what several people said in dragonfly.kernel. Several steps are now removed, but it still has the same flavor.
We had some power outages/surges here because of a windstorm, and my UPS didn’t handle it well, along with other local network equipment. So, I’ll be slow with news posts until I get my internal network in better working order.
This log has been linked on the Downloads page of the DragonFly BSD site.
On a suggestion from Hiten Pandya, I’m going to try to note specific code commits that happen in the dragonfly.commit newsgroup. I’ve not been tracking them too carefully until now.
Apparently this server is colocated somewhere Hurricane Isabel touched down in the US – it was offline for some hours, but seems OK now.
No posts here September 5-7th, as I’ll be out.
I’ve always thought that one of the problems for the various BSD programs is that there’s a lot of good information that can only be found by digging through the various mailing lists. Nobody in their right mind wants to have to sort through the last 3 months of firstname.lastname@example.org just for a 5-second answer. So, blog software used to provide a ‘newsfeed’ may be useful.
I’m not a clever enough programmer to contribute code to DragonFly BSD, but I do read the main newsgroups for it. The DragonFly BSD project is small enough that a rolling readout of events may work. So, I’ve got this blog here to do just that. You too can watch me fumble technical terms!
My first goal is to read up and post. This layout just doesn’t work without an article history, or at least more long-winded articles.