Unofficial accidental “time” theme this week. Also charts!
Lots of event notices in here… Watch for what’s near you.
- The next KnoxBUG meeting is September 5th, with a Trident demo. I’ll post a reminder.
- OpenBSD.Amsterdam. Dedicated OpenBSD/vmd servers, which is a neat idea. Could probably do the same thing with vkernels.
- MeetBSD is happening October 19-20 in Santa Clara, CA. (via)
- Configuring OpenBSD – System and user config files for a more pleasant laptop. Not all of it is OpenBSD-specific. (via)
- Happy Bob’s Libtls tutorial. Also not wholly OpenBSD-specific; more libressl-specific. (via)
- AsiaBSDCon 2019 is happening March 21-24, Tokyo, Japan. (via)
- Ravenports now on gcc 8.2.
- Recent freebsd-jobs posts.
- [talk] ARM – any Tier-1 *BSD options? Nice support work from Netgate.
- libfuzzer, parts 1, 2, and 3 – a Summer of Code project for NetBSD. I linked the first one before, but hadn’t followed up until now. (via)
- OpenBSD, SpamPD and the Startup Bug. (also via)
- Public Access Multics. I am happy just typing that sentence.
tuning(7) had some updates from Matthew Dillon. It’s minor, as he says, but it’s such a useful man page I want to make sure people are reading it.
No interview this week in BSDNow 261, but links to a recent 1999 convention video, details about TrueOS/Project Trident, and the usual.
If you like pizza and BSD, and you are near Portland, Oregon, there’s an event you will enjoy tomorrow night. At least 2 of those 3 characteristics should match you. (via)
Following up on the DragonFly/Threadripper benchmarks, DragonFly now has some NUMA work to accommodate the non-uniform CPU and RAM layout on those boards.
Matthew Dillon (re?)added a sysctl: vfs.hammer2.cluster_write. It defaults to off, since HAMMER2 already writes a large buffer size and this should, in theory, not be needed. It may improve performance in some situations where there’s a lot of file creation and deletion, but that’s my theoretical guess rather than anything I’ve bennchmarked.
There’s several deep dives in the links today; enjoy reading!
Your unrelated music link of the week: A Brief Primer on the Contemporary Glitch-Hop Scene. I liked Tipper more than I expected.
Still haven’t cleared my backlog of links…
This episode has one of the more intriguing titles for BSDNow, and it’s because they are covering a recent hackathon and “BSDCam” (not BSDCan), which I did not know about. The tiny network terminal server mentioned this week may be of use to people, too.
If you haven’t done it before, you can use ‘make rescue’ to build a tiny base system on DragonFly, for use when /usr goes missing, for when your disk is encrypted, and other rather catastrophic problems. It should be in sync with the rest of the system, which is why ‘make rescue’ can be part of a buildworld process. I’m mentioning this because currently, ‘make upgrade’ should be done first.
DragonFly will now run on a Threadripper 2990wx. What’s more, Matthew Dillon has published some testing results showing how power, CPU use, and memory speed all interact with these things. There’s a followup, too. I imagine these are interesting CPUs to most people, since they perform well and don’t have recent Intel-specific security problems.
Done well ahead of time, knowing I’d be on the road this past week.
Overflow from two weeks running, cause of travel.
Intel’s ACPICA 20180810 is now in DragonFly, thanks to Sascha Wildner. Nothing really user-affecting, but it does fix some memory leaks. You can tell it’s very new just by the version number.
Michael W. Lucas is reading from his ‘git commit murder‘ book tonight at 7 PM, in Clawson, Michigan.
BSDNow 259 is out, and I happen to have just come off a 10-hour drive, so I will do nothing other than point you at the episode.
Aaron LI has added interface group support in DragonFly, which is mostly to replace having to name individual interfaces in your pf config. There’s more work done than just that commit, incidentally, and he has a better explanation and writeup than my measly post.
If you have a mangled HAMMER2 disk, and you have inodes that are clearly mangled (the built-in CRCs don’t match), you can now remove them manually. This seems like Hole Hawg territory…