If you have a WhiskeyLake Intel CPU, the i915 driver on DragonFly now recognizes it for hardware acceleration. This will be in the upcoming release.
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.
If you have a NVMe disk that happens to let’s say report inaccurate capabilities (i.e. lie cause it was built cheap), the NVMe driver in DragonFly can now attempt to survive the surprise.
CBSD, the virtualization-management-on-FreeBSD tool could be made to support DragonFly and NVMM. Here’s a tracking issue for it.
DragonFly and Hyper-V’s virtual disk support do not appear to co-operate well, according to this bug report. Anyone have a Hyper-V host where they can confirm?
Longtime readers won’t be surprised by any of the content, but there’s a DragonFly overview at MakeUseOf.
You didn’t need it or use it, but the name itself has a certain symbolism.
If you are running bleeding-edge DragonFly _and_ installed the newest dports binary package build _and_ you are using Samba, you may need to update and rebuild.
Tomohiro Kusumi has removed the old GNU implementation of ext2fs from DragonFly and added the non-GPL-encumbered FreeBSD implementation of ext2fs.
There’s a new build of binary packages for DragonFly, based off the 2021Q4 quarterly ports release. This will require an upgrade of most if not all packages cause of a switch from LibreSSL to OpenSSL as the default SSL library.
Linked here cause maybe it’ll help someone else with synproxy and pf in DragonFly: synproxy state doesn’t work in Packet Filter.
ifconfig(8) in DragonFly is gaining a description field, to ease porting of CBSD.
In Iran, of all places – Google decided this was spam so I am a few days late in posting it to the mirrors page.
The amdgpu driver, equivalent to Linux 4.19, has been committed along with supporting changes in ttm. Credit goes to Sergey Zigachev, Francois Tigeot, and Matthew Dillon for the work. The module is now built by default in bleeding edge DragonFly. Note the amdgpu commit message lists some options that need to be set.
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 upgrade
Don’t forget to update your packages with ‘pkg upgrade’.