Scott Ullrich, who has worked on several BSD-related projects, including DragonFly, has something called vCloudBSD, about which you now know as much as me. It looks to be a FreeBSD auto-installer for virtualization, though I’m sure I’m overgeneralizing.
Hasso Tepper helpfully forwarded announcements for the Call for Papers for both EuroBSDCon 2011 and AsiaBSDCon 2011.
Also, there’s probably going to be DragonFly people at 27C3, and I know there’s going to be some at NYCBSDCon 2010. The early registration discount for NYCBSDCon only lasts about 10 more days, so jump on it while you can; it’s crazy cheap.
I’ve applied on behalf of DragonFly for Google Code-In. It’s similar to Google Summer of Code, but focuses on 13-18-year-olds and smaller tasks. It runs over the year-end, and we’ll know if we’re in by November 5th.
In the meantime, if you have ideas that could fit the program (see task list at the Google site), please put them on the DragonFly project page.
Alex Hornung has some patches that allow KDE4 to build on DragonFly. They aren’t in pkgsrc and not all in KDE yet, so try them out directly if you want KDE4, for now.
Update: based on something Alex said on IRC… they’re in KDE4 now.
The dragonflybsd.org website is a wiki (ikiwiki, to be exact) and any page on it can be edited. You have to create an account, first, which only requires picking a username and password.
However! If you have an account on leaf.dragonflybsd.org where it is hosted, you can check it out via git, edit any number of pages using your favorite editor, and commit it back and the pages will automatically rebuild. The commit will even show up like any other change.
Pratyush Kshirsagar has put together a website describing his proportional RSS work for DragonFly. He may have more content in the future.
DragonFly 2.8 has been branched, with the release anticipated for the end of this month. I’m building packages right now for it, so we should have binary packages ready at release. A convenient git-summarized changelog exists to track differences since 2.7.3, at least.
Venkatesh Srinivas has a large writeup describing just how the memory allocator in DragonFly changed from 2.6 to the upcoming 2.8 version. In all that text, you may notice the cheering statistic that it gave a 20% improvement in sysbench results.
Siju George found no equivalent of OpenBSD’s ‘afterboot‘ quick-start page in DragonFly, so he went and created it himself. Go, read.
YONETANI Tomokazu wrote out a nice explanation of acpi(4) and the myriad ACPI subsystems which can be enabled or disabled at boot time. If you do have booting problems, it’s usually ACPI, and it’s usually only one small part. Finding that small part is easier with this list.
Rumko came up with some changes for vkernel(7) that, among other things, made it possible to run them diskless; almost like booting a thin workstation.
Found via a random Google search: SSHGuard. It’s not available in pkgsrc, but it’s in other BSD packaging systems, and it lists DragonFly on the site as a possible host. It monitors various services and blocks access to overly aggressive connections using (on DragonFly) pf. This is similar to scripts discussed here in the past. It also may be useful in light of the recent FTPd problem.
OpenSSL on DragonFly can now dynamically load engines (cryptographic support modules) at runtime, thanks to Peter Avalos.
Something that always got with with Linux binary support was that I couldn’t get the Linux /proc filesystem to automatically mount on boot. I’d end up doing it by hand later, right after I tried to start a Linux binary and had all sorts of issues. Pierre Abbat had this same problem, and Sascha Wildner has the answer: “linux_load=yes” in /boot/loader.conf.
If you were thinking of buying a Western Digital Passport USB drive, it’s supported on DragonFly, thanks to Dylan Reinhold and Alex Hornung.
For those using the release version of DragonFly, the new C-based loader in 2.8 will look like this. Well, not exactly. This is from a proposal from Alex Hornung that removes some extra lines, but I expect this is what you’ll see.
Matt Dillon and Venkatesh Srinivas conspired to fix another nmalloc issue, which should resolve any remaining problems people were having with Firefox, and possibly other applications as well. Due to an oversight of sorts, all locking operations on nmalloc’s depot were ineffective, as if there were no locking at all. Curiously, it worked remarkably well considering such a large race condition was present.