Another wide range; hope you have reading time.
Your vector graphics video of the week: TANK. (via multiple places)
I have the normal list of links, but here’s a feature. At first glance, this looks like Netgate, the commercial entity behind pfsense, is not using FreeBSD for their new product. However, Jim Thompson of Netgate steps up and give a full-on explanation, and points out there’s already code out there to do this – it needs contributors.
BSDNow 247 leads with a report on Mitchell Horne working for the FreeBSD Foundation (actually in the office) as an intern. It’s an interesting contrast to the all-online model for most committers. There’s plenty more links.
New DragonFly installs are chmod 700 for /root, not 755, from this recent change. Change your existing installation if desired.
If you’ve ever wondered what packages are needed to build a DragonFly release: here they are in one dports metapackage.
I’ve tagged a x.x.1 release – DragonFly 5.2.1, available now. It includes the recently-mentioned fix for CVE-2018-8897 and some other minor updates. See my email to users@ for the details.
A little more on building and less on rights this week.
Note the eleventy-jillion hackathon reports.
Your thinkpiece for the week: The cultural shift from not selling out to blowing up. There’s a BSD analogy possible there.
Sascha Wildner has brought in the last 9 months of ACPICA updates to DragonFly. This may mean better power or motherboard support for your hardware in DragonFly. I always have a hard time pointing directly to ACPICA updates and how they benefit, but looking at the changelog update may help.
BSDNow 246’s title is talking about CVE-2018-8897, which was (unlike the original Spectre/Meltdown) responsibly disclosed to many different operating system vendors, including the BSDs. As a result, fixes arrived a lot faster… seems like a good idea. No interview in this episode, but as always there’s other topics explored.
This commit from Bill Yuan says “highspeed lockless in-kernel NAT”, and lists a huge number of changes for ipfw3. How much of a change is it? I don’t know; there isn’t a matching documentation update and I don’t have a way to test.
I like pointing out how political world events push their way into computer updates.
SemiBUG‘s having a hands-on server workshop tonight. Go, if you are near, and bring something networked to type on.
Thanks to Rimvydas Jasinskas, GCC 8.0 has been imported into DragonFly. It’s not built by default, so you’ll need to set WORLD_ALTCOMPILER to get it. Rimvydas mentions this is part of a 3-year upgrade cycle.
Note that he went the extra mile and made sure dports could handle it too.
I’ve got some real esoteric sources this week.
Your rights-oriented hardware project of the week: NeTV2, a Bunnie Huang project. A neat device worth funding on its own, and worth having to show what capabilities are being denied us by law.
This came together very nicely.
Hey, another terse title, and I didn’t even write it! This BSDNow episode talks about the recent ZFS conference. It’s interesting to think there can be a meetup about a file system that isn’t really held to a vendor at this point. There ‘s a number of other articles, too – I’m just a bit late noting it.
A recent and new CPU bug, CVE-2018-8897, is fixed in DragonFly. THis applies to both Intel and AMD processors. I’m happy to see that the CERT page lists equal notification timing for a whole lot of operating systems, rather than the few that heard about Spectre/Meltdown early.
Following that topic, Matthew Dillon has “fleshed out” Spectre mitigations, and his commit message details the current state. The sysctl ‘machdep.spectre_mitigation’ will tell you what’s set at any given point.
You can now use Wake On LAN functionality with igb(4) cards in DragonFly.
(I like acronymic titles a little too much, I know.)
I managed to miss posting about BSDNow 244, “C is a Lie”. That provocative title is about how C isn’t a low-level language, not that it doesn’t work. Among other things, this week has new-to-me history about the Larrabee architecture, which I only have heard about indirectly.