You can now run devfs(5) and procfs(5) in a jailed environment for DragonFly. As the commit message says, it’s for dsynth but I imagine this may be good for other applications.
If you are running bleeding-edge DragonFly, this recent struct change will require a kernel and world rebuild. If you are running the release, it doesn’t affect you.
New to the DragonFly kernel: jail-like capability restrictions, that may not require a jail to use.
If you pay attention to your daily security run emails on your DragonFly system, you may see entries like this:
+nlookup() at nlookup+0x623 0xffffffff806eff13 +kern_rmdir() at kern_rmdir+0x25 0xffffffff80706db5 +sys_rmdir() at sys_rmdir+0x4c 0xffffffff80706f0c +syscall2() at syscall2+0x11e 0xffffffff80bd9f9e
I see it on the machine where I run this Digest, as the caching mechanism adds and deletes files rapidly. Matthew Dillon has placed it behind a sysctl, so your messages log will be a little less noisy by default.
You can now set a description for a network interface on DragonFly. Don’t use ETH0, please.
If you are using ‘set skip on …’ in your pf config, it used to match any interface that matched the specified type. It now only matches members of that named group. That may change behavior of your pf rules; check the commit to see what to look for.
There’s a new sysctl(8) setting, sysctl.debug, which shows you which sysctl nodes are being requested. I am entertained by the pseudo-recursive style of my explanation.
There’s some bugfixes for HAMMER2 and the kernel that will probably mean a point release soon.
I think I know what Aaron Li might want to work on for DragonFly…
(I am only guessing; I have not asked.)
It’s apparently possible to get a panic by yanking a HAMMER2 disk out of your system, which is only likely when using a USB thumb drive, formatting it to HAMMER2, and not bothering to unmount it. Anyway, that poorly-described-by-me problem is fixed.
There’s an odd bug in ipfw that is now fixed in DragonFly 6.2/6.3. If you are using ipfw and adding networks and hosts in a specific order, the netmask will be set wrong.
There’s also a problem with the overnight bulkfree cleanup in Hammer that’s had various attempts to fix it over time – it’s now really truly fixed. It mattered only if you had an extremely large number of inodes – 100000000 or so,
Matthew Dillon wrote up an explanation for both.