Matthew Dillon’s fixed a possible deadlock in HAMMER2, plus some optimizations that I can’t quantify, but are fun to read about.
If you like csh/tcsh, and also Emacs, there’s a eLisp file to put Emacs in csh script mode, now in DragonFly.
(Someone who uses Emacs more than me tell me if I have a wrong description.)
You may run into a setup issue with Wireguard when trying to set it up on DragonFly. Keep an eye on this Go bug report if so.
Update: here’s a solution in the works.
The drivers amdsmn(4) and amdtemp(4) have received several updates. The output still may have issues, but this is useful if you have newer AMD hardware.
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 have an AR9485 wireless adapter, this bug report notes the appropriate config for DragonFly. Might work for other hardware too?
This query had karu.pruun write a short note on how to contribute (device driver) development work to DragonFly. Don’t forget grok.
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.)
The pageout daemon algorithms in DragonFly have gone through some changes, and Matthew Dillon goes into detail across two commits.
James Cook continues to work on zalloc, and he’s published a small report on his progress.
I’ve mentioned it before, but this recent update to dma in DragonFly reminded me: “dma” stands for DragonFly Mail Agent, a minimal mail agent created for DragonFly as a lighter, local replacement for Sendmail in a base install. But! It’s cross–platform now, and even “upstream” from DragonFly.
James Cook is interested in working on zalloc in DragonFly, taken from the projects page. Follow his questions and the answers if this interests you.
Matthew Dillon implemented POLLHUP for pipes in DragonFly, in -current and 6.0. I mention it because it was for Zig support, and it’s always nice to get a bug report directly from people developing a tool or language.
I’ve seen this a number of times over the years: if you’re installing DragonFly and the install drive seems to disappear, it might be the USB port you plug into.
If you are upgrading an older 5.8.x system to DragonFly 6, and get a lua error when updating pkg: manually copy over a config file, and you’ll be set.
Sascha Wildner has added the PCI IDs for various recent ichsmb(4) devices. This I think just means a correct device name in dmesg, but unidentified smbus devices has plagued me for years, even with other operating systems.
DragoFly 6.0 is tagged and ready for download. There’s ISO images and of course you can upgrade using the notes on the release page. One of the improvements in this release cycle is improved dsynth support, so of course there are many prebuilt packages available; don’t forget to update those too.
There’s only been one issue found in the release candidate so far. It’s fixed, so I’ll tag and build 6.0 within the next few days.
With good timing, 6.x packages are now available for those of you who need them.
Since DragonFly 6.x is a major number change, there’s no prebuilt packages that match that release number. As of this writing, the mirror master site shows 5.10 packages, which would work… if that was the next release. That’s where the number change trips it up. There should be new 6.x packages in the next few days. (Thanks to Jan Peter Vogt for the reminder)