DragonFly’s patch(1) is now at 2.0-12u11. I mention this not because it’s a dramatic change but because it’s a basic tool. Also, a benefit from our new committer.
Welcome Daniel Fojt, our newest committer.
Updates to third-party utilities happen often in DragonFly, and I don’t often link because they may not affect users much – but I’m noting a change to xargs(1) cause given what xargs does, any mistake you make will be repeated many times.
Thanks to Daniel Fojt, wpa_supplicant(8) in DragonFly jumped from version 2.1 to 2.9. There’s a nice changelog for the curious.
Thanks to Aaron LI and Daniel Fojt, libpcap and tcpdump in DragonFly have been updated. The vendor does The Right Thing and provides easy-to-find changelogs for both.
Martin Ivanov has completed his multiboot + DragonFly tutorial. You can read his users@ post on it now, though it should show up in dragonflybsd.org documentation soon.
You can now use newsyslog(8) to rotate logs being written by daemon(8), thanks to this commit from Peeter Must.
tcplay(8) in DragonFly jumped from 2.0 to 3.3. This will be most relevant to you if you encrypt your disks. It’s nice to see DragonFly mentioned specifically on the GitHub source site.
This thread on having a tmpfs /var/run led to this commit, making it as easy as setting a rc.conf variable.
The recent 5.8.1 release of DragonFly includes, among other things, a fix for a de-duplication bug in HAMMER2. If you are curious, here’s the commit / details.
DragonFly 5.8.1 is released, a bugfix update for 5.8.0. The release tag commit has the list of changes, or you can go right to the release page. My users@ post has upgrade instructions.
There’s a couple more small test/debug tools in DragonFly; possibly only useful if you like to poke at internals, but who doesn’t, really?
You can now use ccache to speed up dsynth even more.
Here’s a work in progress: Multiboot installs on DragonFly. Follow the thread for updates.
dhcpcd in DragonFly is updated to 9.0.2. This is a bugfix release, so no new features.
Another network fix: if you have an iwm(4) wireless Intel device, here’s how you get it to stop saying “no carrier”.
If you’ve got an urtwn(4) device (RealTek USB wireless), and you are getting errors on altq_maxlen, take a look at this solution.
Charlotte Koch sent me this link some time ago and I’ve been remiss in not posting it: DragonFly through QEMU, using NVMM, on NetBSD.
This is I think not resolved yet, but here’s something I didn’t know: keeping Chromium from being tied into Google’s services is actually a build issue, not a settings issue. i.e. once it’s in binary form, you can’t opt out.
The Environment Quickstart document for DragonFly now has a HAMMER2 section.