Hubert Feyrer has done a very nice job of collating all the online material from the various presentations, with data from Axel Gruner, that happened at EuroBSDCon 2007.
OpenBSD Journal has an interesting article up that talks about the life cycle of a bug, as seen by an OpenBSD user. I call it interesting because it gives a good summary of a bug-squishing process from a ‘user’ perspective.
Strange as it is to use the words “C compiler” and “excitement” in the same sentence, there’s been a lot of excitement about PCC, the Portable C Compiler, as a faster replacement for GCC. (Previous story here)
There’s a web page for it, and a mailing list, though no mail archive I can find associated with it archived at MARC. (Thanks, Anonymous). The web page has a link to an old PostScript document detailing the original PCC design – there’s something about old Unix manuals from Bell Labs that makes them fun to read.
And of course, there’s always the inevitable Wikipedia page.
In BSDTalk 129, Will Backman talks to Dru Lavigne about BSD Certification and her new job at The Open Source Business Resource.
Matthew Dillon, as part of a larger discussion, chimed in with some sensible descriptions of licensing and how it applies to the recent OpenBSD/Linux kerfuffle.
Noah Yan posted how to apply his recent patch for building an AMD64 kernel. Be warned; it does not create a full usable system – yet.
pcc has been added to NetBSD (via pkgsrc) and OpenBSD, and Steve Mynott has been messing with it on DragonFly. It doesn’t work as a replacement for GCC, but it looks promising. There are other alternatives in progress, too.
This week, BSDTalk talks about sysjail, the Open/NetBSD version of FreeBSD ‘jail’, with Michael Dexter. (Yes, I realize that’s an oversimplification.)
Sepherosa Ziehau has a patch that makes it possible to assign polling(4) to specific CPUs.
Update: There’s a new version of that patch.
If enabling ACPI means that some of the devices attached to your computer can’t be found, YONETANI Tomokazu has a patch that may fix it.
Chris Turner is also a new DragonFly developer with commit access. Welcome, Chris.
DragonFly’s newest developer with commit access: Noah Yan, already known to be working on the AMD64 version of DragonFly. Welcome, Noah.
There’s a good number of commits to DragonFly that I don’t mention on the Digest because they are relatively small, or not necessarily part of a larger plan. However, I’ll take a minute to mention the work by Sascha Wildner; he has kept the man pages in DragonFly up-to-date almost single-handedly, and done an excellent job. How good? See this excerpt from the IRC channel #dragonflybsd on EFNet:
(17:17:57) corecode: wow linux man pages are unreadable
(17:18:00) corecode: incomprehensive
(18:11:52) _hasso_: corecode: linux doesn’t have swildner ;P
YONETANI Tomokazu reports that DragonFly will boot on his Core 2 Duo MacBook Pro, though Daniel Tralamazza reports it won’t boot on his 1st generation MacBook Pro. I didn’t know this was possible…
Update: Darn.
If you haven’t already, you should make sure your NFS mounts can be put into the background. Sooner or later, it’ll save you a lot of waiting.
Dave Hayes posted his scheme for upgrading OpenSSL on a DragonFly 1.8 system to the latest version. This is useful if you haven’t yet moved to 1.10.1, and want to avoid recent OpenSSL security issues.
Linux Weekly News is reporting that AMD is planning to move away from binary driver support to an open-source driver, though the majority of the work will still originate from outside the company. That makes better 3D support on DragonFly at least possible. (via aggelos on EFNet #dragonflybsd)
BSDStats.org is reporting month-on-month increases in the number of reporting clients for almost every BSD flavor; while it’s not the most scientific method of reporting usage numbers, it’s the most scientific one I know of.  It’d be nice to see some more DragonFly hosts in there. (hint hint)
Undeadly.org has more coverage of the ongoing license issues. It is currently halfway between legally serious and Internet drama.
As a followup on the relicensing issue, Theo De Raadt wrote a description of the issues, with his central point: you can’t modify a license (i.e. remove a BSD license) without the agreement of the author. (via Undeadly)
Edit: Changed title for a better description.