Should you need have Ubiquiti devices, and you need to get the Unifi management program running on your DragonFly server, this script will work for you. Some of the filepaths are different, but it’s otherwise complete.
Thanks to Imre Vadasz, your Haswell, Atom SoCs, Skylake, and Kaby Lake CPUs will now recognize the ig4 device on the associated motherboard. I think it does something with ACPI? I have always been hazy on smbus device functions.
Matthew Dillon noted some OpenVPN problems, requiring him to disable compression. I don’t think this is a DragonFly problem, or even necessarily a BSD problem, but it’s worth mentioning in case you run it.
Radeon hardware support in DragonFly has been moved up to match what’s in the Linux 4.7.10 kernel. If you have a R9 290 GPU, there’s some tweaks you may need.
(n.b. may be unnecessary now from later commits; I don’t have the hardware to check.)
Apparently there’s a missing dhclient feature in DragonFly needed to run on OpenStack. Matthew Dillon’s made a change to get it to work – though I can’t find the exact commit.
For some reason I am completely unfamiliar with this standard, but UHS-1 support for Secure Digital cards has been ported to DragonFly by Imre Vadasz, for a limited range of models. UHS stands for “Ultra High Speed”, so perhaps it’s clear what that standard does for you.
Version 1.13.1 of nginx now natively uses CPU affinity on DragonFly. This matches well with SO_REUSEPORT support; I suspect DragonFly is a fantastic place to run nginx at this point.
…And before you say, “It would be great if someone would put together benchmarks”, think instead, “I’m someone, and I could do it.”
Andrew MacIntyre manually installed DragonFly onto a UEFI system, and conveniently he posted his notes. It includes a GRUB menu entry, which will come in handy for someone
There’s a bug with shared libraries in pkg(), which may bite you when upgrading. It’s present in version 1.10.1 at least, so you may want to wait for this fix to be applied before your next upgrade.
If your DragonFly system’s Intel network device doesn’t seem to pick up on DHCP, try turning on polling. This may already be a nonissue, but it doesn’t hurt to mention it.
Update: fixed.
Imre Vadasz added support for ADMA2 transfers in DragonFly. It doesn’t lead to a huge performance boost – yet. It can be turned on and off, but requires Intel chipsets.
Mobile Skylake CPUs appear to have issues with power management and direct video rendering. There’s potential fixes on the horizon, but until then, be aware if you have that specific hardware and software mix.
A tip that might be useful for some readers: Mohammad BadieZadegan posted that he had a poor network connection, and so was having a hard time installing packages. If that bites you too, there are some pkg.conf options – starting with FETCH_TIMEOUT and FETCH_RETRY – that may help.
I noted commits about this before, but here’s the instructions: how to use DragonFly on a Macbook Pro with dual GPUs.
There’s an update for Radeon DRM that matches it up (mostly) to what’s in Linux kernel 4.7.10. If it gives you problems, there’s some workarounds. Remember, this is in DragonFly-current, so anyone running 4.8 is unaffected.
It’s always nice to see this out of nowhere: How to Install DragonFly BSD 4.6 + Xfce Desktop + Apps on VMware.
Francois Tigeot has brought in the ‘apple_gmux’ driver. If you have a Macbook with both Intel and NVIDIA video hardware installed, this driver lets you switch to the Intel hardware, and I assume take advantage of DragonFly’s accelerated i915 driver.
If you are using bhyve, and you want DragonFly on there as a ‘guest’ (not sure if that’s the right term), there’s a template available. (via)
For those of you who build custom kernels, the if_sl, if_ppp, and if_faith devices are now built as modules, not in the kernel. This means you can remove references to them in your custom kernel config – if you have one.