This won’t affect your day-to-day operation of DragonFly, but it’s interesting: apparently, uptime was always (now minus boot time). If you reset the clock on the machine, however, it would no longer be accurate. Now it is accurate, for a number of utilties.
I realized I never followed up on the call for testing: re(4) driver updates from Sepherosa Ziehau were indeed tested and found good, so the driver has been updated.
One last thing sneaking in for the week: There’s an update for libressl in DragonFly that fixes CVE-2020-1971. It’s there for 5.8 or -current.
The next release of DragonFly will be 6.0, mostly because 5.10 is an annoying version number rather than any significant version changes. We’re due to release by the biannual calendar schedule – but there’s a DRI bug that needs to be fixed; I plan to tag as soon as that’s done.
If you have a Realtek network card supported by the re(4) driver, Sepherosa Ziehau has a new driver for you to test.
Because of this commit that makes some changes to lib/stdio, you might get more reinstalls than you expect on your next pkg upgrade because of the __DragonFly_version change. This only applies to -current (5.9) users.
(I might be wrong)
If you want to build a kernel with no options, stripped down, here you go. I don’t know how useful it would be…
Matthew Dillon has made significant changes to the callout API in DragonFly. Interesting to look at, but I think no changes from a user point of view.
I’ve seen this multiple times over the years: if ifconfig suddenly stops working, especially after an upgrade. your kernel and world are out of sync. Rebuild and make sure you get both updated.
DragonFly has a new version of libressl, noting cause it has a newer TLS1.3 implementation – something that may be necessary for you.
If you’ve got a Zen 2 / Ryzen 4000 APU, the amdsmn(4)/amdtemp(4) drivers in DragonFly now support it.
There’s a minor update to dhcpcd in DragonFly, which may be of specific interest if you’re on an IPv4/IPv6 network – there’s a Preferred option added for that.
binutils and ld in DragonFly have been set to binutils234 and ld.bfd temporarily, for what appears to be work with the EFI bootloader. This should not make a difference for normal use; rebuilding binaries will give you different results but they’ll run.
cpdup(1) will now exactly recreate symlinks. That may be helpful for your backup strategy if it already involves cpdup.
Well, it doesn’t fix anything, but it seems like an answer that almost always helps: running sysmouse usually fixes most X11 mouse problems.
You can now use compilers.conf(5) to switch to clang10/llvm10 for building Dragonfly. Untested yet!
This seems so minor, but such a good idea: a regular check to make sure kernel and userland are in sync.
Daniel Fojt’s updated libedit in DragonFly; not huge, but I mention it cause I’ve seen the very first bug fixed in the commit listing; garbled history.
Matthew Dillon added “existence locks” to DragonFly, which as usual he committed with a long, descriptive message.
There’s now -K (kernel) and -U (user env) options to uname. Minor, but good to know the change.