There’s a Youtube video showing how to set up a virtual kernel on DragonFly. I don’t think I linked to this before. (via)
Nuno Antunes has committed a large quantity of work on updating netgraph to version 7. His goal is to be able to run mpd5, though it’s not there yet. If you want to look at it, go to the monthly page and look around the 10th; there’s too much to link to individually.
Peter Avalos has updated OpenSSL to 1.0.0f; this is to fix 6 security issues identified in the OpenSSL changelog.
I just mentioned DNSSEC in last week’s Lazy Reading, and here’s a “How to get DNSSEC with BIND 9.8.1 working” article from Michael Lucas. It’s pretty simple… Conveniently, BIND 9.8.1 is available in pkgsrc as net/bind98.
You may want to update for this – a lockup bug with the re(4) (RealTek 8xxx series) driver has been fixed.
dma, which originated on DragonFly, is now at version 0.7, and so is the version in DragonFly.
If you’re running DragonFly on a very low-end system, you may be wondering about memory requirements for Hammer. Hammer is much less RAM-hungry than ZFS, so it looks like you can get away with 128M, as long as you don’t mind the occasional error message. You can manually tweak settings for it if you like. 256M is plenty.
It still strikes me as odd to consider systems with less than 1G of RAM as “low-memory”. What rich times we live in!
John Marino updated libm, bringing a large quantity of functions. This may be a stopgap measure for now. As a positive side effect, buffer overflow attacks are a bit harder now.
Chris Turner got it working on i386, at least, and his post will help you do the same. I don’t know if these changes have made it through to pkgsrc or for x86_64 yet.
That’s Managed System Interrupts, for when your hardware is passing a lot of data and generating a lot of corresponding hardware interrupts. MSI is what deals with all that traffic. High-bandwidth (10G) network cards, for instance. Anyway, Sepherosa Ziehau’s made more commits than what I’m linking to here, for support with various devices.
There’s many other MSIs out there, oddly enough.
Are you going to Chaos Communication Congress 28? There’s going to be a number of DragonFly developers there, so it’s a good time to meet up. They’re in EFNet #dragonflybsd IRC, so speak up there if you want to find them.
The recently discovered telnetd vulnerability has been fixed in DragonFly, thanks to Peter Avalos. Apparently it’s been around everywhere forever. (last link via xhr) Hopefully there aren’t that many people that still need a telnet daemon; SSH has run it out of town for the most part.
Since I’m already talking about imports, several changes from FreeBSD and OpenBSD for NFS, plus more original material, have been brought in by Venkatesh Srinivas. Those changes from FreeBSD apparently improve NFS write performance, though I don’t have numbers to show.
There’s been a rare segfault present in DragonFly for quite some time. It’s been difficult to reproduce, and the 2.12 release due some months ago was held up specifically to fix it. Matthew Dillon was, after many days (months?) of work, able to replicate it reliably and eventually find a way around what appears to be a new AMD-specific bug. Read his very detailed explanation of what he did to get to this point.
Francois Tigeot benchmarked his accounting work with blogbench, and posted a PDF with the results. Dmitrij D. Czarkoff made a simpler graph, which can be used to draw the conclusion: blogbench didn’t work well for estimating the impact of VFS accounting. If you want to try accounting yourself, put vfs.accounting_enabled="1" in your /boot/loader.conf.
(The normal DragonFly mailarchive isn’t updating because it feeds from DragonFly NNTP, and that’s not updating, so I’m using Gmane for post links.)
There is now a NO_BINUTILS221 option, added by Sascha Wildner, that will keep your system from building binutils 2.21 during a buildworld. The system will still build binutils 2.22, so there will still be a functioning ld on the system. Use this along with NO_GCC41 (so only gcc 4.4 gets built) to speed up your buildworlds, if you like.
There’s a new DragonFly mirror, in Colorado, USA – at dragonflybsd.mirrorcatalogs.com. It’s on the mirrors page on the DragonFly site, too.
If you’re looking to use IPMI and remotely watch the console of another system, Matthew Dillon has made some changes to help with that.
Sepherosa Ziehau has added updated the ‘ecc’ device, for Intel E3-1200 series systems. What’s it do? It will report on memory errors, and potentially fix them.
You should have ECC memory in your server already. If not, you oughta.
Update: as Sascha Wildner pointed out, ecc(4) already existed, but didn’t support Intel controllers. Also, the Xeon X3400 series is supported now too.