BSDNews has an interesting link to a Inquirer article benchmarking the new Intel processors.Â While it does wander into excessive acronyms, it’s interesting that the benchmarking is done using a variety of BSDs.
Matthew Dillon reported that DragonFly Preview code (version 1.7) have been synchronized with the bleeding-edge code, as it’s been stable.Â Also, the 1.8 release is definitely scheduled for January, at which point he plans to have “at least a basic userland kernel binary”.
‘nega’ reports a DragonFly 1.4 has gone for most of a year without issue; good news for an operating system undergoing heavy surgery.
A fellow named Trismegistos is interested in creating an Italian BSD community; if you’re interested, contact him at firstname.lastname@example.org.
Something less obvious about the open source model (and, of course, the DragonFly project) is the relatively egalitarian playing field for anyone who wants to contribute.Â The worst thing that can happen is a rude email.Â Via Slashdot comes the story of how a simple menu was too long and still
Mike Tancsa is doing some throughput testing on different versions of FreeBSD, Linux, and DragonFly.Â DragonFly does relatively well for a system in the middle of a dramatic change.
The new site look has been extended to wiki.dragonflybsd.org, the CVSWeb output, and the mail archive. Also, usage of the bug tracker has increased lately, with a significant reduction in the number of outstanding bugs. If you do happen to have any pending bugs reports on the tracker (which includes posts to the bugs@ mailing list), please update or close them.
The latest bsdtalk (which I mention far less than I should) has a talk with pkgsrc developer Johnny Lam.
Recently on the pkgsrc tech-pkg list, Roland Illig posted the developer-oriented “How to get help with pkgsrc / pkgsrc documentation“, and Alistair Crooks posted “Changes to the Packages Collection in October 2006“.
Erik Wikstrom wrote up a mini-tutorial about cvsup, for those who want to know.
dragonflybsd.org has been given a makeover, by yours truly.