Remember how I said dsynth defaults to txz (tarred, XZipped) ? I was apparently wrong and it was using tgz (tarred, gnuzipped). Now it really truly defaults to txz, for space.
There’s a vulnerability in file(1), CVE-2019-18218. It’s fixed in current and release versions of DragonFly. Update when you get a chance.
I thought this would happen: the nrelease(7) process can use binary packages to build DragonFly. (For the dports packages, not the base system.) This is very interesting to me, but also useful for anyone who wants to build a custom DragonFly; something I think more people could do.
This may be of most interest to me, since I’m usually the one building DragonFly releases. nrelease(7), which is used to build each release of DragonFly, now sticks to the default kernel config, and may use binary packages in the future. There’s some other changes but these are the ones I can describe most exactly; there might be more on the way.
If you were used to kldloading i915kms(4) and radeonkms(4)… they are now named i915 and radeon, respectively.
Pluggable Authentication Modules on DragonFly have gone through some changes. pam_ssh has been removed, along with pam_tacplus, and pam_radius, in favor of the more frequently updated versions in dports. ppp(8) still supports radius, though.
There’s now (well, for DragonFly 5.7 users) an /etc/os-release file to show the installed DragonFly version. This is similar to the de facto Linux standard, which of course evolved separately from the not-consistently implemented general standard. Evolved cross-platform standards are fine with me.
If you have a whole lot of I/O on a HAMMER2 system, this change will help. This is I assume an outgrowth of dsynth testing, cause that causes many, many threads to be reading and writing.
Tomohiro Kusumi has been bringing in a large number of fixes to the msdos filesystem, mostly from FreeBSD, but from other sources. I’m not going to link to them all, cause there’s many over the last few weeks, but the good news is that there’s performance gains for this lowest-common-denominator filesystem.
dsynth(1) has a new ‘monitor’ command, which watches log output and tells you what it’s doing. I haven’t tried it yet, so I am only guessing. A screenshot would be nice.
The default variables for jails on DragonFly have changed; obviously this only affects you if you are running jails. Adjust your rc.conf as needed.
A quick entry: dhcpcd(8) 8.0.6. committed to DragonFly.
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 not familiar with utmp(5) and utmpx(5), they are databases in /var that track user logins and system restarts. utmpx is of course better cause it has an X.
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.
ABI breakage continues, so continue the full buildworld/buildkernel cycle, if you are on DragonFly-current, and continue to ignore it, if you are on 5.6.
Update: yeah aim for next week.
Roy Marples has imported openresolv 3.9.2 to DragonFly. This is a replacement for the old-style /etc/resolv.conf file. The more complicated your network, the more you will appreciate this tool.