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.
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.
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?
dhcpcd in DragonFly is updated to 9.0.2. This is a bugfix release, so no new features.
Imported directly by the author, DragonFly now has dhcpcd 9. The commit message lists changes.
(and there’s a 9.0.1)
Even if you run bash, zsh, or maybe fish, tcsh is the default root shell in DragonFly – and it just had an update. (all bugfixes according to the release notes)
The ssh-copy-id utility is now included in DragonFly 5.8 and in -current. Useful for your next machine setup.
This doesn’t really have any effect on you unless you are programming on DragonFly, but it’s interesting to read about a “spinlock trick” Matthew Dillon had implemented recently.
Aaron LI’s updated the development(7) man page to account for new steps in vendor import.
Aaron LI managed to graft FreeBSD code history onto the DragonFly BSD git repository, and he’s documented how he did it. So, you can follow DragonFly code all the way back to 2003, and then FreeBSD code all the way back to… I’m not sure how far back it goes, but it’s in his merged copy.
Flame graphs are a way to see what code paths are most used in a stack trace. DragonFly now has a flame_graph utility.
Jails on DragonFly can now route to loopback addresses (i.e. 127.0.0.1). Because of this, they can work like shared IPs and the jail can connect to the host.
I think this means that you no longer have to bind jail services to specific IPs as you did previously. Don’t quote me on that; I’ve run few jails in my life.
Update: I should have linked this too: the sysctl jail.defaults.allow_listen_override that makes it easier in the host system too.
On EFNet #dragonflybsd, Matthew Dillon and ‘mjg’ have been discussing various way to optimize for bulk builds. A recent update from mjg for different memory functions shaved 1.7% off bulk build time – significant, when you are talking tens of thousands of packages.
binutils 2.25 is out, binutils 2.34 is in. The binutils upgrade happened just before the 5.8 branch, so it’s in the 5.8 release – though 2.27 is still the default.
One side effect of repeated package builds is that you start looking at ways to optimize for intense, repeated, parallel software compilation.