I’m going to be very busy over the next week, so I am not sure how consistent my posting schedule will be, or how much I will be able to build up for next weekend. We’ll find out together.
You’ll all be happy to know ACPI errors are less noisy now. (And it was updated to 20190509, before the 5.6 release.)
This week’s BSD Now talks about the normal assortment of news, including DragonFly’s release, and an explanation of the Vulkan framework in OpenBSD; something I hadn’t read about yet.
Matthew Dillon’s made a change to the DragonFly kernel that could be disruptive, but will help make sure chromium runs. If you update after this point, make sure to update your dports, too, just to be sure everything is in sync. This applies to 5.6 and 5.7.
Because of some changes Matthew Dillon made to maxvnodes calculation in DragonFly, you may find yourself using 5%-10% less RAM. If you’ve upgraded to 5.6, you already have this benefit.
DragonFly now has retpoline turned on (stats included in that link) as a side effect of having gcc-8 as default, and SMAP/SMEP are also supported. I enjoy just saying these words out loud. SMEP SMEP SMEP SMEPSMEPSMEPSMEP.
I’m still backlogged, so here’s a May 14th mitigation in DragonFly for MDS attacks possible with Intel CPUs from 2011 onward. It’s in the current release.
Lots of topic range this week; no theme grew out – but that’s better in some ways!
A happy note for the end of the week: I like seeing cross-BSD work. (and POSIX)
This week’s BSD Now talks a whole lot about ZFS, which is no surprise given the OpenZFS events going on. There’s other news, of course.
Shamelessly copied from my own users@ post: I tagged 5.6.1 and built it earlier today. This version has a corrected sshd_config and fixes a lockup bug in ttm. The ISO should be showing up on mirror-master.dragonflybsd.org in the next 20 minutes or so, or you can rebuild using the normal process on an existing 5.6 system:
If you are still on 5.4 or earlier, you need to bring in 5.6 sources, which is noted in the 5.6.0 announcement.
A last-minute drm change in DragonFly 5.6 turned out to cause a reproducible lockup, so there’s changes in place for it. This means 5.6.1 will need to be rolled, which I will do in a day or two. If you want to update now, the normal buildworld/buildkernel process will get you this change.
OPIE was disabled recently in DragonFly. Now that the 5.6 release is out, it has been removed. This may require manual intervention if you are on DragonFly-master (i.e. 5.5. or 5.7) and update in the next day or two. This need to fiddle with it will go away soon with changes to ‘make upgrade’; I will mention it when I see it.
This won’t affect anyone running 5.4 or 5.6. It’s only in development.
Matt Parnell is presenting Asterisk and FreePBX on FreeBSD at SEMIBUG’s monthly meeting, tomorrow, in Troy, Michigan. Go, if you are near.
Credit goes to SEMIBUG for creating a Google Calendar which makes it slightly more likely I’ll catch the meeting and post about it. Also, a nostalgia moment about the bad old days: I am so glad specialized hardware is no longer needed just to get on the phone network, since VoIP is widespread these days. I hated dealing with flaky PRI lines.
DragonFly 5.6.0 has been released. This version brings an improved virtual memory system, updates to radeon and ttm, and performance improvements for HAMMER2. Matthew Dillon did some informal testing of the VM improvements, and posted results to the users@ list.
My users@ post has the usual details on upgrading (pay no attention to my 5.4 typo), as do the release notes.
Inadvertent theme this week: games. Yet somehow I didn’t include a roguelike? Dang.
I linked to some other BSD link roundups, so the joy of clicking can continue.
Francois Tigeot updated ttm and radeon DRM in DragonFly to match what’s in I assume the Linux 3.18 kernel. Please try if you have the appropriate hardware. This was at the start of May, so you may have already done so without realizing if you run -current. It’ll be in the 5.6 release, too.