If you are trying to use both NAT and IPv6 with pf on DragonFly, there was a bug (seen here with FreeBSD) with :0 where it would use link-local addresses. It’s now fixed.
If you are using ‘set skip on …’ in your pf config, it used to match any interface that matched the specified type. It now only matches members of that named group. That may change behavior of your pf rules; check the commit to see what to look for.
There’s a new sysctl(8) setting, sysctl.debug, which shows you which sysctl nodes are being requested. I am entertained by the pseudo-recursive style of my explanation.
There’s some bugfixes for HAMMER2 and the kernel that will probably mean a point release soon.
I think I know what Aaron Li might want to work on for DragonFly…
(I am only guessing; I have not asked.)
It’s apparently possible to get a panic by yanking a HAMMER2 disk out of your system, which is only likely when using a USB thumb drive, formatting it to HAMMER2, and not bothering to unmount it. Anyway, that poorly-described-by-me problem is fixed.
There’s an odd bug in ipfw that is now fixed in DragonFly 6.2/6.3. If you are using ipfw and adding networks and hosts in a specific order, the netmask will be set wrong.
There’s also a problem with the overnight bulkfree cleanup in Hammer that’s had various attempts to fix it over time – it’s now really truly fixed. It mattered only if you had an extremely large number of inodes – 100000000 or so,
Matthew Dillon wrote up an explanation for both.
I use date(1) just rarely enough that I can never remember the right arguments to create a human-readable result. Now, there’s an -I arg to date(1) that uses a word instead of a format string to get ISO8601 output.
I realize my title is a little bit buffalo buffalo buffalo, but it makes sense: getopt(3) now has a double colon option to indicate an optional argument. I link to it because I like seeing the length of the trip to DragonFly. It started as a GNU option, then showed up in NetBSD, brought to FreeBSD, and now I’m posting about it.
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.
You didn’t need it or use it, but the name itself has a certain symbolism.
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.
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:
make buildworld
make buildkernel
make installkernel
make installworld
make upgradeDon’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.