The headline is a little misleading; umtpx has been in DragonFly forever, but now utmp is really retired and programs adjusted to match. The change is not that user-affecting and utmp data is still accessible; this is part of the ABI change alluded to over the past week.
If you are on DragonFly-current, the ABI changes of the past few days are complete and new dports packages are built, so now is a good time to do a complete build and install of world and kernel, and then a pkg update.
5.6 users can keep on keeping on; no breakage there.
First, history: DragonFly has had binaries of dports available for download for quite some time. These were originally built using poudriere, and then using the synth tool put together by John Marino. Synth worked both to build all software in dports, and as a way to test DragonFly’s SMP capability under extreme load.
Matthew Dillon is working on a new version, called dsynth. It is available now but not yet part of the build. He’s been working quickly on it and there’s plenty more commits than what I have linked here. It’s already led to finding more high-load fixes.
Here’s something I haven’t see before: at the time of me typing this, there are commits in DragonFly, FreeBSD, and I assume NetBSD (haven’t found the commit), but the 2019-5612 CVE entry is still shown as reserved and not public. This may change by the time you read this article, of course.
Update: the original source, found by an intrepid reader.
This slipped in just before the 5.6 release, and I thought I had already noted it: DragonFly now defaults to HAMMER2 for disks during install, instead of HAMMER1.
There’s now a read-only sysctl ‘jail.jailed’ that can be checked to see if the current environment is running within a jail; useful for scripts that should not run in that environment, etc. I link to it mostly because it’s an odd sort of meta-signifier of reality, like being awake or in a waking dream, and that entertains me.
DragonFly’s tcp keepalive was changed from milliseconds to seconds. This happened in both DragonFly-current and in the 5.6 release, and it changes the networking API, which means a dports rebuild is needed… or a pkg upgrade, for which happily all packages have been rebuilt. So, on your next update of the system, be sure to update packages too.
The module formerly known as ‘radeonkms’ is now just plain ‘radeon’. There have been changes in other commits, but this is the only usage change.