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.
I’m talking about DragonFly at SEMIBUG’s online meeting (using Jitsi) tomorrow.
UPDATE: https://meet.jit.si/SEMI-BUGDragonFlyBSD is the Jitsi link. It’ll be 7 PM Eastern time.
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.
Sandy River is the newest DragonFly mirror, with ISOs and dports packages.
It’s based off 2022Q1 from FreeBSD Ports, and it’s available now through pkg.
There’s a new page on the DragonFly site covering how to install DragonFly as a guest system under KVM.
If you run pkg on DragonFly and get a warning about “Meta v1 support ending”, it’s only a warning. It will go away on its own.
I know I’ll need this again, so I am making a post out of it. If you are running a DragonFly system through NVMM using the excellent site instructions, and you want X apps to display on a local Windows workstation, you need to:
- Install VcXsrv (or your X server of choice) on Windows and start it up.
- Install xauth and xterm on the DragonFly host.
- On the DragonFly host, set these three options in /etc/ssh/sshd_config. They are already there but commented out with different arguments.
X11Forwarding yes X11DisplayOffset 0 X11UseLocalhost yes
- Reload sshd: ‘service sshd reload’.
- ‘Enable X11 Forwarding’ under Connection -> SSH -> X11 in the puTTY setup dialog.
Connect to the DragonFly host with puTTY, type ‘xterm’, and a terminal window should appear on your Windows desktop within a few seconds. This could be turned into a shortcut with puTTY to avoid having redundant terminals, but I’m not writing that out yet.
I use date(1) just rarely enough that I can never remember the right arguments to create a human-readable result. Now, there’s an -I arg to date(1) that uses a word instead of a format string to get ISO8601 output.
I realize my title is a little bit buffalo buffalo buffalo, but it makes sense: getopt(3) now has a double colon option to indicate an optional argument. I link to it because I like seeing the length of the trip to DragonFly. It started as a GNU option, then showed up in NetBSD, brought to FreeBSD, and now I’m posting about it.
This is pretty esoteric, but all of DragonFly’s syscalls can be found in the links Aaron LI provided in this post. There’s code in there that dates back to Berkley UNIX.
If you are using AMD graphics on DragonFly, Aaron LI’s “how I set this up” post may be useful to you.
There’s a reported bug with NVMM and QEMU if you boot a guest using UEFI. Until it’s fixed, use BIOS.
It may be because I am a nerd but I enjoy reading detailed explanations of bugfixes like this one for HAMMER2. This fix is present in the 6.2 release, of course.