It may be because I am a nerd but I enjoy reading detailed explanations of bugfixes like this one for HAMMER2. This fix is present in the 6.2 release, of course.
I tagged DragonFly 6.2, and I’m planning for release later this week. Release notes and ISO/IMGs to come with the release, as usual.
Tomohiro Kusumi has removed the old GNU implementation of ext2fs from DragonFly and added the non-GPL-encumbered FreeBSD implementation of ext2fs.
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.
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:
make buildworld make buildkernel make installkernel make installworld make upgrade
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.
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.
The version of qemu in dports is not set up to support this, yet. Until then, you can download a prebuilt version.
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.
Thanks to yrabbit, there’s a full FPGA toolchain possible on DragonFly. It’s preliminary, but it works.