With the new 0.10.0 release of Qemu, it’s a bit easier to get it running on DragonFly. Hasso Tepper asks that anyone who patched Qemu to run it on a DragonFly system send him the patches. He can get them into pkgsrc, and upstream.
(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.
Happy Cube day!
– Producing Open Source Software, which I find interesting, and it’s available in dead tree form and as a free download. This fits with some conversations I’ve had recently.
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.
I’ll mention this briefly, since it’s off-topic: I’m looking for a new job, and it should come as no surprise that I’d like to work with BSD systems. (resume as PDF)
The March issue of the Open Source Business Resource is out, with the topic being “Geospatial” – something that isn’t covered often in open source terms.
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.