Emiel Kollof warns that the newest binary driver from NVIDIA is now FreeBSD-5 specific, and so does not yet work on DragonFly. If you’ve got a working driver now, don’t upgrade.
UnixReview.com has 2 new book reviews available: one on “Slamming Spam: A Guide for System Administrators” and one on “Disaster Recovery Yellow Pages“.
If you’re going to USENIX this week, tell Matthew Dillon. If time permits, he’ll be setting up a DragonFly BoF session, in addition to presenting a paper in Kirk McKusick’s session.
Brad Harvell posted a link to a torrent for the 1.2 DragonFly release.
NetBSD’s first quarter report is out. Some of it’s already been linked here.
Matthew Dillon warned that a number of new, destabilizing technologies are going to be entering the bleeding edge DragonFly code, otherwise known as HEAD. Unless you enjoy trouble, the PREVIEW-tagged code (formerly known as STABLE) is a better target.
Correct tags to use in your CVSup files are named on the Download page.
If you’ve got lots of bandwidth and you’d like to provide a mirror for the upcoming release, contact Matthew Dillon.
BSD Updates is apparently planning to extend the binary updates service to all major BSD flavors – Net, Open, and, most importantly, DragonFly. (Thanks BSDNews) The BSDNews article mentions only NetBSD and OpenBSD, but the website mentions DragonFly.
ONLamp.com/BSD has a new “The Month in BSD” article up, covering March.
Joerg Sonnenberger is talking about a major change to libc, after this upcoming release. Follow the thread for some interesting comments on versioning, including Matthew Dillon wishing there was more Matthew Dillons in the world.
The CVS tag for the next release, “DragonFly_RELEASE_1_2” has been placed, which means commits are OK again.
There is a prerelease version of 1.2 on gobsd.com via HTTP or FTP, and also at pfsense.com via HTTP. Here’s the MD5:
MD5 (dfly-20050406-pre1.2.iso.gz) = 9b382c84e629b391bd4ce38c7ca724bd
If you can bear waiting, I would advise waiting for the official release later this week, just in case something is found in the next day or two.
Jeroen Ruigrok/asmodai has put together a standards conformance checklist for DragonFly. If you want to tackle something on it, let him know.
Joerg Sonneberger pointed at this batch script for building ports in a jail, so that the building process cannot crap out while your installed ports are in flux.
Jeremy C. Reed is looking for a DragonFly host to use for bulk-building pkgsrc. He’d need about 20G of space, and an open port for reports through http.
I have a computer for it, but no connection yet. He mentions in his post (linked above) that currently, just over 40% of packages in pkgsrc build on DragonFly, which works out to over 2,000 programs.
Matthew Dillon slipped the stable tag again, to get a few more bugfixes in.
He also discovered some problems with the OpenBSD version of NTPd currently in base; it will probably be replaced or significantly changed at some point after this upcoming release.
Matthew Dillon, while examining another problem, added a webstress program, which tests making many, many connections to a http server.
He also committed a related program, wildcardinfo, which lists wildcard hash tables for each CPU in the system.
The stable tag has been slipped again; there is still a few issues to work out.
Matthew Dillon also described his plans for release schedules.
If you were trying pkgsrc but having trouble building gtk2 (and therefore Gnome), Todd Willeyt has placed a binary of pkgsrc gtk2 on gobsd.com, and is trying to get the appropriate changes made upstream.
Sascha Wildner has created a DragonFly Artwork section on the wiki; upload if you got some!
Naming each version of DragonFly has been under discussion in kernel@ for a while; Matthew Dillon posted a changed naming plan based on all this talk.