I saved this but forgot to post it just before the 6.0.1 release: DragonFly now has OpenSSH 8.8p1. The OpenSSH release notes mention that SHA-1 RSA
keys signatures (thanks, Ross Richardson for the correction) will no longer work, along with other updates. You are hopefully already using something else.
xdisk is now being built by default, and libdmsg is able to encrypt/decrypt with a placeholder scheme.
Yes, this means you can mount remote Hammer2 disks as a block device. Read the man pages and remember this is experimental.
You can now create FAT volumes on DragonFly. Not exactly high-tech, but a filesystem that most anything can read and write.
6.0.1 is tagged and available. The major reason for this update is an expired Let’s Encrypt certificate that would cause problems when downloading dpkg binaries. A list of 6.0.1 commits is available.
I recommend the usual rebuild process mentioned on the 6.0 release notes:
Don’t forget to update your packages with ‘pkg upgrade’.
If you have encountered that problem with Let’s Encrypt and dports, the fix is committed and a make world is needed.
If libvirt running with nvmm on DragonFly interests you, watch this bug report.
Not huge news about mandoc, but I always like linking to updates with clear changelists.
It used to be that if you had a HAMMER2 volume and ran low on space, snapshotting would stop so that you didn’t completely fill the disk. Now, thanks to Francis GUDIN, snapshots continue to roll forward and discard older ones to keep disk usage constant. It won’t fix the low disk space issue, but snapshots will stay up to date. It’s in 6.0 too.
If you think about the name, you’ll realize what it does: libpasswdqc(8) does quality checks on passwords via PAM, and now it’s in DragonFly.
Aaron LI’s added NVMM, hardware acceleration for virtual machines, to DragonFly.
The version of qemu in dports is not set up to support this, yet. Until then, you can download a prebuilt version.
Since NVMM originated on NetBSD, the NetBSD documentation page for it describes how to use it quite well. There’s a man page in DragonFly for it too, of course. There’s even basic machines to try.
boot and libstand directories are moved to src/stand/boot on DragonFly. This won’t affect most people, as you’ll upgrade and build the same way as always, but if you were specifically looking for it in the old locations of sys/boot and lib/libstand, you’d be surprised.
I didn’t know about this, but there’s a daily/weekly/monthly/security_show_badconfig option in periodic.conf that is now defaulting to “yes” in DragonFly. This I assume means you’ll get the output of erroring periodic scripts sent to you. Useful, especially if you find out about an error you hadn’t seen before.
covid(1), the program, from NetBSD and now in DragonFly.
Here’s a link to a commit for dsynth that gives an idea of how huge a debug build of chromium can be.
Thanks to yrabbit, there’s a full FPGA toolchain possible on DragonFly. It’s preliminary, but it works.
Matthew Dillon’s merged a good number of patches from -current DragonFly to the 6.0 branch. No emergency items, but it’s a good time to update.
Judging from this large number of commits talking about NVMM support, Aaron Li is bringing NVMM from NetBSD to DragonFly. And here’s some minor statistics.
Matthew Dillon’s fixed a possible deadlock in HAMMER2, plus some optimizations that I can’t quantify, but are fun to read about.
It’s worth saying because people don’t realize it: In-code documentation updates, even if the code itself isn’t changed, is a worthwhile way to contribute.
If you are one of those unlucky/foolhardy people running DragonFly with very little RAM, this maxvnodes change will help you out.
(DragonFly is not that RAM-hungry in normal circumstances, anyway; 1-2G is ‘safe’, last I knew.)