I didn’t realize this before, but you could not mount a nullfs(5) or tempfs(5) filesystem within a jail(8) on DragonFly… until now.
If you’ve ever been left watching a “press any key…” line at shutdown of your DragonFly system, there’s now a fix. It’s committed to release, too, so it’s available now.
While you’re at it, there’s a HAMMER2 bugfix that will also be brought in by updating.
It hasn’t been updated or used for some time, but libc_r was 20+ years old. Now it’s gone. You know someone younger than this code, or maybe even younger than the last time I talked about it.
If you are like me, you’ve typed “make buildworld && make buildkernel && make installkernel …” about a zillion times. Now, you can encapsulate that process in a shorter statement: ‘make build-all install-all‘. The real benefit is these new steps also run in parallel to match the number of CPUs present, and logs to file instead of the console, automatically.
Some of the larger application sets on DragonFly have had trouble building, and inconsistent problems with that build. i.e. rust would fail, but in different parts of the build process, every time. It looks to be a problem with signal interaction, and there’s now much safer ways to do that on DragonFly.
That is going to require a full buildworld/buildkernel if you are on DragonFly-master, 5.7. Release/5.6 users are unaffected.
I link because they are good: 10% speedup. Or, because they made me laugh: “Basically, don’t use this.”
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.