The DCBSDCon site, for the BSD convention in Washington, DC, Feb 5th-6th, now has a separate blog. The very first post lets slip the name of their first speaker and the fact that they will have 2 separate BSDA exams at the convention.
Michael Neumann created a patch that can get VirtualBox to run DragonFly, kinda sorta. The underlying issue in Virtualbox is not fixed by this, however..
I don’t know if this is going to be the long-term solution, as discussion is ongoing, but the existing commit mail format has been explained.
Stumbled on via Google Alerts: Freebench, a new benchmarking program that has already been tested on DragonFly. (Scroll down to “Freebenchin'”.)
Hasso Tepper has a copy of cgit running for DragonFly’s git repository, and I’ve set up the same thing on leaf.
I added BSDanywhere to the blogroll – it’s another livecd BSD ‘distribution’, this time with OpenBSD as the base. Also, Jibbed, which is the same arrangement using NetBSD.
When creating the 2.1 tag in git, Simon ‘corecode’ Schubert also auto-created a message showing every commit ever, grouped by committer, with the first line of each commit. Reading through it provides an interesting look at what particular itch different people have scratched with DragonFly, over the years. (Also available as a plain count.)
Matthew Dillon’s updated Hammer to create two new directives: ‘version’ and ‘version-upgrade’, along with a number of internal changes and fixes.
Simon ‘corecode’ Schubert warns that a recent change in the size of struct thread is going to require a buildworld; this only affects people running DragonFly 2.1.
The new switch to git has brought out a lot of new committer activity; nothing to point you at specifically, but it’s nice to see that it has encouraged action.
Jason Dixon posted that today is the last day to submit papers for the DCBSDCon. So you’re either done, really close to done, or not getting anything in this year, at this point.
Sepherosa Ziehau has another test patch for optimizing network speed; he’s looking for (but not exclusively) ipv6 users. It’s pretty safe, though it will require a quickworld.
- Simon ‘corecode’ Schubert suggests summarizing your changes in the first line of your commit message, as that first line gets used by other tools that read from git.
- Peter Avalos has set up a (speedy!) North American mirror of the DragonFly git repo.
- Aggelos Economopoulos has been adding Git tips for DragonFly to a page on the wiki.
The Git repositiory for DragonFly is up and running, and Simon ‘corecode’ Schubert asks people to use a mirror. The update messages to commit@ are working. There’s places to see the repo via the web, too.
Instructions for using Git to access DragonFly source for users and committers has been posted, with a special note on the origin tag. However, it’s not quite ready yet…
The latest BSDTalk is a 23-minute conversation with Asterisk Open Source Community Director John Todd.
These positions where someone works for a company, specifically to interact with a community of people who may produce unpaid work for that company, intrigue me.
Thanks to the efforts of Hasso Tepper, support for the FreeDesktop HAL (hardware abstraction layer) using the bleeding-edge versions of DragonFly and pkgsrc is available.
Hasso Tepper recently finished a bulk build of pkgsrc on DragonFly 2.1, with only just under 5% of packages actually failing to build. I think the “natural” average is around 3%-4% just from the natural disorder of over 8,000 3rd party software packages, so this is an excellent state to be in.
I’m working on a new set of 2.0.1 pkgsrc packages for download from pkgbox, incidentally.
Lazy Sunday? Running carp? Why not try Sepherosa Ziehau’s carp patch? No, I don’t know what it does.
Dru Lavigne’s got a link to the slides from the recent MeetBSD event, plus links to video of her presentation.