There’s a couple more small test/debug tools in DragonFly; possibly only useful if you like to poke at internals, but who doesn’t, really?
Here’s a work in progress: Multiboot installs on DragonFly. Follow the thread for updates.
dhcpcd in DragonFly is updated to 9.0.2. This is a bugfix release, so no new features.
Another network fix: if you have an iwm(4) wireless Intel device, here’s how you get it to stop saying “no carrier”.
If you’ve got an urtwn(4) device (RealTek USB wireless), and you are getting errors on altq_maxlen, take a look at this solution.
Charlotte Koch sent me this link some time ago and I’ve been remiss in not posting it: DragonFly through QEMU, using NVMM, on NetBSD.
This is I think not resolved yet, but here’s something I didn’t know: keeping Chromium from being tied into Google’s services is actually a build issue, not a settings issue. i.e. once it’s in binary form, you can’t opt out.
The Environment Quickstart document for DragonFly now has a HAMMER2 section.
Do you still reflexively type “shutdown -p now” to power down your computer? I haven’t been able to break that habit. A recent documentation commit reminded me that “poweroff” exists, even though I posted about it 7 years ago.
If you want to work on Bluetooth on DragonFly, there’s more people adding to the bounty.
sysmouse, the one mouse driver for X that always works for me, now has evdev support.
Related: why is there no evdev man page in DragonFly?
Imported directly by the author, DragonFly now has dhcpcd 9. The commit message lists changes.
(and there’s a 9.0.1)
Even if you run bash, zsh, or maybe fish, tcsh is the default root shell in DragonFly – and it just had an update. (all bugfixes according to the release notes)
karu.pruun posted an answer on how to get DragonFly onto your GPT/EFI drive.
The ssh-copy-id utility is now included in DragonFly 5.8 and in -current. Useful for your next machine setup.
This doesn’t really have any effect on you unless you are programming on DragonFly, but it’s interesting to read about a “spinlock trick” Matthew Dillon had implemented recently.
Aaron LI’s updated the development(7) man page to account for new steps in vendor import.
Aaron LI managed to graft FreeBSD code history onto the DragonFly BSD git repository, and he’s documented how he did it. So, you can follow DragonFly code all the way back to 2003, and then FreeBSD code all the way back to… I’m not sure how far back it goes, but it’s in his merged copy.
Flame graphs are a way to see what code paths are most used in a stack trace. DragonFly now has a flame_graph utility.