Back to overflow, which sort of makes my life easier.
- BCHS: BSD, C, httpd, SQLite. Linked before, so comments on source links are where to look if you are already familiar with BHCS.
- Possible stack vulnerabilities in BSD-land.
- How to disable cores in OpenBSD?
- Nextcloud via httpd on OpenBSD. (via)
- MP-safe Networking in NetBSD. PDF, from BSDCan. (via)
- BSDCan 2017 Recap from iXSystems.
- Unix in Europe: between innovation, diffusion and heritage. October 19th, Paris, France. (via)
- The Stack Clash, via many places.
- pkgsrcCon 2017, in one week.
- PCIe adapters supporting long distance 10GB fiber? Note that this is for BSD-based, server-based routers. Follow the thread for lots of hardware talk.
- OpenBSD now has Trapsleds to make life harder for ROPers.
Even more overflow, pushing my pre-published posts forward.
There’s been enough this week I’ve already started next week’s BSD entry.
A good topic range this week.
It’s long article title week!
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)
All done at the last minute!
Odd batch of links this week.
Your BSD-related fiction book of the week (year? decade?) :’git commit murder‘ is out, set at a (fictional) BSD convention.
More thinking topics than version changes this week, which is interesting.
Slightly short this week, maybe because people are prepping for AsiaBSDCon? I have plenty of links for tomorrow’s Lazy Reading.
Reminder: the 2017 FreeBSD Storage Summit is tomorrow.
I measure the success of In Other BSDs by how many different BSD flavors I can reference. This is a good week.
Lots of storage this week.
Rimvydas Jasinskas posted an extended description of what’s happening with dports. There’s a significant xorg reformatting coming in ports, which is going to be absorbed into dports, but it may take some time. There’s also an odd loss of commit rights for John Marino, who commits (frequently!) to both DragonFly and FreeBSD. (His followup) This all translates to some upcoming transition time for dports to accommodate these changes.
Note that if you are using dports binaries, especially on DragonFly 4.6 release, this won’t really affect you; the way dports is set up, binary sets always work. It is interesting to hear about future work, in any case.
A lot of the real content this week is buried in the comments, strangely.