No new groups … yet

Probably in part because of a long-running off-topic SCO thread in dragonfly.kernel, ‘trent’ suggested an advocacy or general group. Matt Dillon said “in a few months, just prior to the first release”.

No contrib changes

In a conversation about updating bind, several people noted that changes other than vendor updates to contrib can wait until there’s a complete packaging system in place. (i.e. things like bind and sendmail are staying in place, for now.)

Start cleanly

There’s been a number of people reporting various breakages during install or boot time. To weed out problems caused by old data right away, remember to:

rm -rf /usr/obj
make buildworld
make buildkernel
make installkernel
make installworld
mergemaster
reboot

An interesting confluence

Michal Ostrowski, a developer with the K42 project at IBM Research, posted to dragonfly.kernel and noted that DragonFly and K42 are very similar in design and could benefit from interaction. He brought up several papers located on their site: a K42 overview, K42 and traditional UNIX APIs, and K42’s threading and scheduling infrastructure. The closely-related Tornado operating system also has some good information.

I’ve been playing too much Day of Defeat; I see ‘KAR98‘ every time I read K42. The project’s not about a teutonic WW2 rifle, though – the name K42 has a different origin.

SCO hints at widening suit

Jeroen Ruigrok pointed out this Newsforge article that says SCO will probably be bringing the AT&T settlement over BSD into court. According to people’s opinions, however, this is a last legal flailing, rather than anything that will significantly affect BSD-derived systems like DragonFly.

Daemonnews also has a mention of this, where Marc Rassbach points out the article’s author has a ‘poison pen’ history vs. BSD products, and Peter Hansteen notes a Forbes article on SCO, this Byte article, and the ever-bearded Greg Lehey’s excellent appraisal of this mess.

Release styles

According to Matt Dillon, DragonFly will skip the multiple branch style of FreeBSD (STABLE, CURRENT branches) and tag the single main branch, slipping as needed for security fixes.

1.0-CURRENT

Aaaand it’s done – rebuilding your system with current sources will give you a uname that reports “DragonFly”. Through some trickery, most ports are apparently not broken by this.

Name breakage

Matt Dillon’s bringing in the ‘DragonFly’ name to replace ‘FreeBSD’ in the source, which may break a number of things over the next few days, including all ports.

Light reading

Joshua Coombs asked about good books for BSD kernel/network programming. Jeroen Ruigrok listed: “The Design and Implementation of 4.4BSD”, “Unix Internals: The New Frontiers”, and “The Design of the Unix Operating System”.

DrASCIIFly

From Joshua Coombs:

          _  _
          ()()
 _________|  |_________
(_________\  /_________)
(_________/  \_________)
       __/|  |\__
          |  |
           ||
           ||
           ||
           \/

Slow going

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.