This hasn’t been as clearly noted as it could be: there’s a DragonFly channel on IRC: #dragonflybsd on EFNet, with a steady population of users and developers. Please drop in.
I just finished the application for DragonFly to participate in Summer of Code 2009:
We did well last year, so I’m hoping we will get in again. Check the website for this year’s details.
Big news: Sepherosa Ziehau has managed to remove the Big Giant Lock from the ip and bridge forwarding path. This includes ipfw, though not yet pf. It is in fact possible to make the whole TCP/UDP code path BGL-free. Sepeherosa helpfully posted some benchmarks to show just how significant the improvements can be.
- ‘alexh’ put in a new page on dragonflybsd.org, describing how you can contribute to DragonFly.
- ‘jth’ has been making a huge number of fixes for the Handbook pages, for links I missed in conversion.
- If you have projects for Google Summer of Code 2009, or can work as a student or mentor, put it on the SoC 2009 page, as a number of people have been doing.
wiki.dragonflybsd.org has been set to be read-only, since the content has been moved to www.dragonflybsd.org. The site hasn’t been turned off yet, because I may have missed something in the move…
(I’m especially happy about the concept of complete man pages, having been frustrated today by a newly installed Linux system that lacked man pages to match the installed drivers or utilities for the intended hardware. Yeah, I’m talking AsteriskNOW.)
If you were looking to create a very large or very small version of the DragonFly logo, I’ve added .eps and .ai versions of the logo to the images page on the DragonFly website.
The iwi(4) firmware has been updated, and there’s an announcement that tells you where to find it.
If you are interested in the Google Summer of Code project, as a student, a mentor, or just want to suggest a project, write that down:
The application period starts for DragonFly (for the organization, not students) in a week, and it’ll help to see who wants to get in on the action.
Daniel Phillips, who is working on the Tux3 filesystem, posted some more design notes. For those who joined recently, Tux3 is a filesystem similar in some ways to Hammer but being designed for Linux as its primary platform. This is a massively complex idea and project, so it’s good to peruse both the Tux3 site and prior posts about it.
Simon ‘corecode’ Schubert has some tips on how to mirror the git repo for DragonFly more exactly; there’s an additional command that can clean up spurious branches.
Sepherosa Ziehau has added a preference for the emx(4) driver over em(4). This means that loading the emx module or adding the emx device to your kernel config will may turn your em devices into emx. This isn’t dangerous; just a note to keep it from being a surprise.
Edit: Thanks, Sascha Wildner, for pointing out details on which chipsets are affected.
Matthew Dillon notes that a 2.2.1 release will be coming about halfway through March; being a minor release, it’ll be bugfixes for things like the installer and the Hammer undo utility.
Alex Hornung posted a description of the work he’s done so far on a new I/O scheduler, with some details on his ideas on multiple scheduler levels. Feedback is welcomed.
RUE Beltelecom has a DragonFly mirror; it includes images, snapshots, and binary packages. It’s already listed on the download page on the DragonFly website, too.