BSDTalk 141 has Kris Moore from PC-BSD talking about their recent release 4 of PC-BSD’s packaging system, PBI.
Looking at the general information page from Google and this OnLAMP article, it appears that Google’s new phone operating system, Android, is based both on Linux (the kernel) and OpenBSD/NetBSD (libc). I wonder how much of the GNU tools are on there.
I also wonder what moved them to that decision. Part of the Android FAQ section points at this article about the Apache License (a BSD-style license) being preferable.
Matthew Dillon’s latest HAMMER update covers the last 3 items needed, and it’s almost-but-not-quite testing time.
Microsoft has made announcements about interoperability with open source and their products. Lots of analysis of this is happening, though I like chromatic’s summary best.
‘walt’ passed along a note about his success using grub2 to boot DragonFly.
Ohloh.net keeps statistics for a variety of open-source projects, including DragonFly. It tells a story mostly based on source code analysis. Which committer for DragonFly has the least commits? Me! Of course, it’s my news articles from this blog that show up on the project page, so it’s missing out on what I’ve heard called the “atmosphere” around open source projects. Hubert Feyrer seems to think the same way.
Puget Sound Technologies is holding a training class for BSDA (as in BSD Associate) certification down in Texas in late April. The teacher, Jeremy C. Reed, has contributed to DragonFly, among other things. (Via BSDNews)
The most recent FreeBSD progress report is out; among other things, it talks about work on multi-IPv4/IPv6 jails, TCP cleanup, and TCP reassembly optimization.  Interestingly, I think there’s related work in DragonFly – the DragonFly jail changes were about a year ago, and Jeff Hsu’s work on the DragonFly network stack seems similar.
I doubt there’s many people on the planet with the brainpower and time for this, but it would be interesting to have a large-scare compare/contrast of the different BSD styles for solving problems in code.
Dru Lavigne’s latest blog post has a pile of good links in it; I’m just going to point at it and tell you to make with the clicking.
As Hasso Tepper describes in a kernel@ post, the recent FreeBSD IPSEC issue affected DragonFly too, but was fixed in a previous release.
InformIT has an article about alternative compilers, including some that have had mention on the DragonFly lists, like TenDRA and pcc. (via Hubert Feyrer)
For those who want a quick reference: regular expression cheat sheets. Of course, it’s not such a quick reference if there’s 11 sheets. (Found via rootprompt.org)
On a side note: I consider Mastering Regular Expressions one of those books that delivers what the title promised.
OnLAMP.com has an 2-page interview of Bruce Perens, Eric Raymond, Brian Behlendorf, and Michael Tiemann, all about 10 years of the Open Source Initiative. (Not the OSI model as my headline may suggest.)
Hey, the NetBSD mail archives have been redone, and are much more readable. The pkgsrc lists like pkgsrc-users are there, and possibly useful to DragonFly users. Interestingly, they are using the same support programs to create the archive as we are.(via Hubert Feyrer)
Dru Lavigne’s “Creating a Publication Using Open Source Tools” talk at SCALE 2008 is available as a PDF.
Matthew Dillon posted another HAMMER summary. This one details the great success he has had simplifying his strategy. Here’s some details on what didn’t work, for the curious.
Here’s a rather long list of various closed-source programs and the open-source alternatives that match them. (Via Hubert Feyrer)
The real advancement for open-source is going to be when they are no longer the second choice. It’ll make my day when I see throwaway articles like “Tired of the GIMP and have money to burn? Why not Photoshop?”
By common consensus on the kernel@ mailing lists, the next release will be 1.12. (Everyone wants to have HAMMER fully tested before 2.0) The 1.12 code branch is happening today.
Bruce Perens has put together a summary for the first decade of open source. It’s a call to arms, not a news report. though that should not be a surprise.
This being a BSD-centric publication, I have to quibble: He defines open source as having started by his writing about it, 10 years ago, which seems somewhat arbitrary. Also, he claims the GPLv3 is the ‘strongest’ open source license possible on the basis that people have been looking at it. I’d argue that the BSD license has already made it through court.  The biggest problem these days appears to be patent law, which is certainly vulnerable to challenge. (Via OnLAMP)