IPSEC hasn’t been maintained in basically forever in DragonFly, so it’s been removed. It was only still mentioned in the VKERNEL configs, so if you have a custom VKERNEL config file, remove any mention of IPSEC, IPSEC_ESP, or IPSEC_DEBUG. Otherwise, nothing to worry about.
I like code that travels through multiple BSDs.
I haven’t been able to say this in a while, but: I like cross-pollination.
For anyone wanting to try out ipfw3, there’s now a rc script. Make sure to set up a rules file, or you’ll kill all incoming traffic.
According to Tomohiro Kusumi, libfuse compiles on DragonFly. This is only one-half of the equation, however. Kernel-side FUSE needs to be ported in order to use FUSE-based filesystems, so there’s a project ripe for the taking…
I branched DragonFly 5.2 last night, and built a release candidate, which should be available at most any mirror by now. If no surprises turn up, the release should be this weekend or a little after, because of the holiday.
BSDStats was in DragonFly as a default-to-disabled rc script. It’s been removed. It’s still available, and updatable, in the form of the dport. The bsdstats.org website should have more info about what it does. (though the site appears to be down right now)
Sepherosa Ziehau presented on DragonFly’s network stack at the just-concluded AsiaBSDCon 2018. He posted a link to the badges, his paper, and his slides.
If you are using virtio drivers, there’s no longer a need for ‘device virtio_pci’ in your kernel config. It’s autoloaded as a dependency. If you run a custom kernel, remember to take it out. You’ll want to do that now if you’re on 5.1, or later at the next version upgrade if you are on 5.0.
The default options on the math/py-numpy port slowed it down. Francois Tigeot noticed, and committed a change that takes advantage of all processors. Read his note to users@ for details.
Remember: there’s a separate document about porting FreeBSD drivers to DragonFly. I note it cause it’s useful and because Rimvydas Jasinskas just updated it.
This isn’t really a dramatic event, but Rimvydas Jasinskas has added support for DWARF-4 line number tables in binutils 2.27. I am linking it to remind everyone that a little bit of Tolkien, in the form of elves (elfs?) and dwarfs (dwarves?) lives in your computer. We need a ORC standard. Oh. Hobbit? Hobbit.
Tomohiro Kusumi has brought in exFAT support to DragonFly from FreeBSD. Useful for cross-platform drives when FAT32 isn’t enough, and NTFS brings its own problems.
If you don’t have an Intel CPU, but still want to perform microcode updates, cpucontrol(8) now supports more recent AMD CPUs.
Rimvydas Jasinskas created a loader.conf(5) hint that keeps various nata(4) devices from attaching during boot. This is super useful if it’s a device that screws up your boot process. and I think it’s also great if you get irritated having something in your dmesg every time about the device you never use, like a CDROM.
The ls(1) command has a lot of options (Look at the man page synopsis!). So much so, that the most recent option added in DragonFly is “_”. That’s to show nanotime as part of the -l output. This will be most useful when you have multiple files being created within the same second of time, and you want to see which came first.
I’m still catching up with the pre-2018, pre-Meltdown commits, so here’s one: Changing the staged packet count in DragonFly changes forwarding rate, for the better – up to a point. There’s probably some specific ratio in the change that makes sense, though I don’t know it.
The commands rcp(1), rlogin(1), rlogind(1), rsh(1) and rshd(1) have been removed from DragonFly. There’s a net/bsdrcmds port if you still need them… though I imagine/hope ssh is filling the void for everyone.
I’m sure this was needed by someone: morse(6) can now encode and decode Morse code, signified by . and – of course.
Matthew Dillon posted a summary of IBRS and IBPB support in DragonFly, and some numbers showing its impact in various configurations of options and CPUs.