Imre Vadasz is working on full-offload scan support for wlan, imported from FreeBSD. That doesn’t change much from a user point of view, other that (I assume) reducing load and power usage a tiny amount. I’m reinforcing something most people don’t think about: there’s tiny computers inside your computer with their own firmware and processors, that you don’t directly control.
It’s now possible to put the /boot of your DragonFly system in the ‘a’ partition of a disklabel. It’s perhaps not major, but it’s another step in EFI support. EFI installs are possible now – if you do it manually.
Remember I posted that LibreSSL is in base DragonFly, but not default? Well, it’s default now. You can have a system without OpenSSL at all, by rebuilding DragonFly-current and using up-to-date dports.
Update: see John’s comments for clarification: LibreSSL is default; the change is that OpenSSL isn’t even built any more. The result is still the same good news: you can have an OpenSSL-free DragonFly system now.
I don’t have it uploaded yet, but DragonFly 4.6.1 is tagged. Anyone with an existing 4.6.0 or earlier system can upgrade now. Use the 4.6 release instructions if you are unsure on how to upgrade. The 4.6.1 tag commit message has all the changes.
If you had trouble getting your laptop’s touchpad to work under DragonFly, try again. (If you are running DragonFly-current)
It’s now possible to build dports using LibreSSL instead of OpenSSL. Set SSL_DEFAULT in make.conf to the appropriate port name, and start building. Use synth for fastest results, of course.
LibreSSL will eventually become the default library. This is in addition to the previously-mentioned, already-completed in DragonFly 4.7, base system switch to LibreSSL.
Matthew Dillon has added powerd, a utility that will automatically step down processor speed based on reported temperature. The range is configurable, and there’s some other nice-to-have features. This will save your CPU from melting, and probably also your thighs from being burned.
Recent changes for virtual machine support and the new powerd utility have been rolled into the release branch for DragonFly. They’ll probably be in the next point release, or you can rebuild a release machine now for immediate access.
Also mentioned in the update from Matthew Dillon, DragonFly-master users should upgrade carefully as DragonFly migrates to using LibreSSL in base, and dports-based LibreSSL in dports.
If you are on DragonFly-current, AKA DragonFly 4.7, make sure to perform a full buildworld on your next upgrade. Tomohiro Kusumi changed a Hammer ioctl, and the buildworld is needed to keep everything in sync.