Even more Meltdown

Are you tired of hearing about Meltdown/Spectre yet?  Doesn’t matter!  The two sysctls for controlling mitigation in DragonFly have been renamed:

machdep.meltdown_mitigation
machdep.spectre_mitigation

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.

DragonFly donations

DragonFly has a donation page and a Paypal account.  There’s no 501c3 benefit for U.S. residents to donate; DragonFly doesn’t exist as a non-profit.  People have still been donating in smaller sums over time.  It’s not enough to offset the colocation fees ($4k/year) plus the hardware there, but the money does get used for specific tasks.  Matthew Dillon wrote a description of his upcoming plans: more storage, plus some interesting details on how much wear the existing SSD disks have sustained.

DragonFly 4.9 users and dports

Because of the major version number change, there’s no packages built for DragonFly 4.9.  Your options are to either update to 5.1 (which you probably meant to do anyway if you are running current) or manually point to the newest packages.  Or just build from dports.

For clarity, this does not affect you at all if you are running 5.0 release.  It only affects you if you are running DragonFly-current and have not updated in a while.