This is going to seem minor, but it’s been annoying for a zillion years, and now it’s fixed: mail(1) now reflows text properly after a screen resize.
iwm(4) on DragonFly has been updated, mostly with patches from the FreeBSD version of the network driver.
/proc/self/exe now exists on DragonFly. This is probably most useful if you are porting software.
It took almost 3 decades, but it’s much harder to shoot yourself in the foot with ping now.
Aaron LI’s written up a nice summary of what’s been added to support WireGuard on DragonFly and how to get started. You need to be on -master to use it, but if you want to read about it there’s always the man page.
There’s a huge amount of commits for this, but I’ll point at the first with FreeBSD code; one of several incorporating OpenBSD changes, and of course it rolls out to tools.
The DragonFly release process now includes an automatic build of supporting packages.
Aaron Li has committed different crypto implementations for support.
You can now run devfs(5) and procfs(5) in a jailed environment for DragonFly. As the commit message says, it’s for dsynth but I imagine this may be good for other applications.
If you are running bleeding-edge DragonFly, this recent struct change will require a kernel and world rebuild. If you are running the release, it doesn’t affect you.
New to the DragonFly kernel: jail-like capability restrictions, that may not require a jail to use.
Tomohiro Kusumi’s offline HAMMER2 support continues, with ‘setcheck’ (check code) and ‘setcomp’ (compression type) support. See the hammer2(8) man page for what those options do.
You can now clean up, grow, and destroy HAMMER2 volumes, even when they are not mounted. There’s also an emergency mode, though I’m not clear on when you’d invoke it.
This will matter most to you if your connection to the Internet is poor: fetch(1) now will time out on data transfers too.
Welcome Sergey Zigachev, new DragonFly committer who has already committed an amdgpu fix.
If you pay attention to your daily security run emails on your DragonFly system, you may see entries like this:
+nlookup() at nlookup+0x623 0xffffffff806eff13 +kern_rmdir() at kern_rmdir+0x25 0xffffffff80706db5 +sys_rmdir() at sys_rmdir+0x4c 0xffffffff80706f0c +syscall2() at syscall2+0x11e 0xffffffff80bd9f9e
I see it on the machine where I run this Digest, as the caching mechanism adds and deletes files rapidly. Matthew Dillon has placed it behind a sysctl, so your messages log will be a little less noisy by default.
makefs(8) now supports HAMMER2 on DragonFly, so you can create HAMMER2 file system images, same as a CD image or a DOS disk.
mlockall(2) in DragonFly has been revamped for compatibility with other implementations. This should have no obvious end user impact, other than a bit easier to port stuff. I want to mention it to note the work done.