There’s been some conversations about getting OpenVPN to work, though it’s still not complete.
Stefan Krüger’s writeup of how to do a stress test on DragonFly is now on the wiki.
Stefan Krüger has written up a nice description of how to use Peter Holm’s kernel stress test on DragonFly.
UnixReview.com has a much larger than normal set of new (new since I last linked) articles up; instead of linking to individual ones, I’ll just say “go visit“.
Due to a disk problem, some of the archived mailing list messages/articles on the news server are missing. The mail archives appear OK, however.
Preview, the halfway step between ‘safe’ and bleeding edge code in DragonFly, is due for an update soon.
Ever have your console filled with messages from some bizarre hardware issue? Bill Hacker knows how to fix it.
Max von Seibold identified a nice installation guide for DragonFly. (His other question about bootblocks is answered later.)
Chris Csandy offers these helpful tips on how to build a bridge.
If you’re looking for some extra small programming work, Matthew Dillon suggests teaching inetd to bind to one interface like in OpenBSD, or allowing userspace threads to pick a CPU on which to run.
wiki.dragonflybsd.org is now pointing at a new site hosted by fortunaty.net. It also includes this new Device HOWTO by Thomas Schlesinger.
Simon ‘corecode’ Schubert has added a change that makes cvs ask for confirmation before using a filename when adding a commit message.
BSDCertification.org has released their report for 2005. The link is to a press release; the actual report is a PDF. (Thanks, BSDNews.)
Hubert Feyrer posted links to a BSDCan 2006 talk on BSD Live CDs, a subject near and dear to my heart. (I’d like to see a DragonFly Live CD that included X and a variety of applications, like PC-BSD or Desktop BSD.)
Matthew Dillon has found that an extended form of spinlock is useful for the MP goals he has to do before continuing his VFS work.
Matthew Dillon found some problems in his ongoing vnode work. Apparently, the way to solve them is to make other portions of the code multiprocessor safe.
This week, on UnixReview.com: the book reviews of “Extrusion Detection: Security Monitoring for Internal Intrusions” and “Linux Patch Management“, and more on security certification.
If you’re concerned about (or involved in) device documentation, there’s a new wiki site called Vendor Watch, which lists the state of efforts to get different hardware vendors to document their hardware in a way that makes it usable for open source efforts.
BSDCertification.org has a new logo and a new competition where the best fundraising idea from a user group gets a prize (passes to BSDCan 2007). June 10th is the cutoff for registering your group. (thanks, BSDNews)
I missed this before: BSDTalk has an interview with Scott Ullrich, who has worked on DragonFly and the BSD Installer, among other things. There’s lots of other recent interviews, too.