Another across-the-BSDs week.
Oh, hey, that’s a nice thing to say. (via tuxillo on EFNet #dragonflybsd)
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.
Sepherosa Ziehau published a PDF that shows the impact of Spectre and Meltdown mitigations on network performance. It’s as bad as anticipated. If this is a problem for you, remember the sysctl machdep.isolated_user_pmap turns these changes on and off.
If you don’t have an Intel CPU, but still want to perform microcode updates, cpucontrol(8) now supports more recent AMD CPUs.
The default kernel config for DragonFly has changed: Sascha Wildner has added the acpi, gpio_acpi, gpio_intel, smbus and smbacp devices. If you are using a custom kernel, you’ll probably want to add these. If you aren’t using a custom kernel – you should have no negative effect.
Sepherosa Ziehau’s updated the em(4) driver for Intel network cards, with the 7.6.2 release directly from Intel. For once, Intel news not related to CPU hardware bugs.
The title really says it all – if you have a Coffee Lake series Intel chipset, your video is accelerated on DragonFly.
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.
DragonFly now has support for the Adaptec 1420. “Now” means since last month, cause I am working through my link backlog.
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.
I say “one more” like I know when this saga will end. If you are using the devcpu-data port to update your processors, you’ll need to add
to your /etc/rc.conf, as Sepherosa Ziehau points out.
The regular maintenance scripts for HAMMER1 assume that it’s mounted at the time of cleanup. If you have them unmounted, they won’t go through that regular maintenance, but it’s easy enough to fix.
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.
Are you tired of hearing about Meltdown/Spectre yet? Doesn’t matter! The two sysctls for controlling mitigation in DragonFly have been renamed:
They go to hopefully sensible defaults, but Matthew Dillon has done some testing to show the effects of each in various combinations. (Update: more changes and tests.) Note that this is not the final mitigation work; compilers (i.e. gcc) are being updated to include workarounds for this, so new gcc -> new compiler in DragonFly -> new defenses. No silver bullet there, though.