I mentioned a new committer for DragonFly, Sergey Zigachev, recently. He hasn’t shown in the commit logs for DragonFly directly – cause he’s fixing up dports. I’m mentioning that because the amount of work that goes into dports to keep all those ports working on DragonFly is separate and unseen – but necessary.
Welcome Sergey Zigachev, new DragonFly committer who has already committed an amdgpu fix.
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.
makefs(8) now supports HAMMER2 on DragonFly, so you can create HAMMER2 file system images, same as a CD image or a DOS disk.
When you are setting up a DragonFly machine on Hetzner, pay attention to this bug report for dhcp setup. The short answer is “use dhcpcd”.
Ian Grindley has created a BSD theme for rEFInd that covers all the BSDs – including DragonFly.
An interesting thought: since HAMMER2 is intended to be a multi-master file system, it has to figure out – and quickly – which is the most up to date versions of any given file. That means you could have multiple versions of a file existing at the same time until that decision is made. That wouldn’t be visible from a user perspective.
Hopefully there’s a new ISO/img on the mirrors for DragonFly 6.2.2 by the time you read this – or you can just update your installation. The changelog is short, because this is a bugfix-level release. Also, don’t forget there’s a new set of binary packages out; update that too if you haven’t.
If you’re interested in having virtio_console on DragonFly, keep an eye on this bug report.
There’s a new dports build, and there’s been some updates so a new point release to 6.2.2 for DragonFly is a good idea. The new binary packages are available now with ‘pkg upgrade’, and I’ll work on 6.2.2 over the next few days.
mlockall(2) in DragonFly has been revamped for compatibility with other implementations. This should have no obvious end user impact, other than a bit easier to port stuff. I want to mention it to note the work done.
You can now set a description for a network interface on DragonFly. Don’t use ETH0, please.
If you are trying to use both NAT and IPv6 with pf on DragonFly, there was a bug (seen here with FreeBSD) with :0 where it would use link-local addresses. It’s now fixed.
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.
Headlines from this here Digest show up on dragonflybsd.org, and have for a long time. They are now joined with reports from the continuous integration builds of DragonFly (i.e. Jenkins) DragonFly is automatically rebuilt to test recent commits, and there’s a report for each build on the build machine.
I think I know what Aaron Li might want to work on for DragonFly…
(I am only guessing; I have not asked.)
If you want to run DragonFly as a bhyve guest using UEFI, here’s the recipe.