A running description of activity related to DragonFly BSD.
Here’s something I haven’t see before: at the time of me typing this, there are commits in DragonFly, FreeBSD, and I assume NetBSD (haven’t found the commit), but the 2019-5612 CVE entry is still shown as reserved and not public. This may change by the time you read this article, of course.
Update: the original source, found by an intrepid reader.
If you have an AM4 motherboard and also can’t EFI boot DragonFly on it, this recent change may fix that for you.
Also, if you are using a Corsair keyboard, this commit may be useful to you.
Matthew Dillon posted an extensive writeup about the hardware changes for dragonflybsd.org; price to performance ratio has been improving so much for multiprocessor machines that we can jump forward both for hosting hardware and for a testbed.
He also mentions his immediate thoughts on what to tackle next, since SMP has been so relentless improved in DragonFly. It resulted in a very long conversational chain as people weighed in with opinions, so I’ve held off posting it until the conversation finished. (I chimed in too.)
Again, way behind cause of being online only irregularly over the last week. There’s still plenty to look at – August is made for Lazy Reading.
This is a somewhat pre-made post coming off a week on the road, so I packed it chock-full.
Roy Marples, the ‘upstream‘ for dhcpcd(8), noticed that DragonFly was working with it as a dhclient/rtsold replacement, but the process wasn’t complete. So … welcome new committer!
DragonFly’s tap(4)/tun(4) devices have been historically precreated – tap0, tap1, tap2, tap3. They are now auto-cloned, which might surprise any software counting on the prior behavior. I don’t know of any specific packages that are affected by this, though. DragonFly version 5.6 is unaffected by this; it’s in -current only.
If you upgrade DragonFly and one of the shared libraries used by pkg gets updated, you can’t run pkg until you get files, but pkg is the program you use to bring in new files. This chicken-and-egg problem is solved with pkg-static, a version of pkg built without shared libraries.
You may have noticed some format flip-flopping between pkg and pkg-static if you had to run it after the most recent DragonFly upgrade; that is fixed. There’s a larger issue of certificate installation identified there; I don’t know a solution to it, but I do want to mention this for next time pkg breaks for someone – pkg-static will work as backup, including to bring in a new version of pkg.
I’m posting this late cause I was traveling when it went up: BSD Now 310 is a nice cross-BSD roundup this week. I might miss the next BSD Now too, so don’t wait for me to link to it.
The monthly ChiBUG meeting is tomorrow, at the usual place. RSVP to the mailing list if you are going. And you should go, just to find out what hardware Joshua Stein is working on right now.
Because of the recent tcp keepalive change and some other updates, DragonFly 5.6 has been updated to 5.6.2. See my release email, and update the normal way. You will need to update your installed dports.
I have some neat history items mixed in this week.
Your unrelated music of the week: Blarf: Cease and Desist. (via)
A reminder: if you have a BSD user group and I’m not posting about your meetings, please make sure I know about it.
When you encrypt your DragonFly boot drive, initrd(7) is run to get your system online and able to accept a password to decrypt the drive. So far, so good. The initrd program is a minimal userland designed to be small, and it generally works. However, it assumes a QWERTY keyboard. If you’re Pierre-Alain TORET and normally use an AZERTY (in this case French) keyboard, that makes it difficult to type the decryption phrase.
It’s possible to patch a different keyboard layout into initrd, and he has documented just how to do that.
Remember my post about a new upgrade script? tse, the author, has happily added in a bunch of suggestions. I’m intermittently traveling and can’t do anything to test it for days yet – but I’d love to see others try it out.
The bugs issue tracking versions is here: #3197. Can you, dear reader, try it out? Do an in-place upgrade on your version, or even a test install with a VM? I want to see what happens in the wild.
DragonFly has a utility called kcollect(8), for gathering about the last day’s worth of kernel statistics. It recently gained some extra flags and details, and should work well if you want to collect stats in a low-impact way.
Andre Buskvekster is presenting at NYCBUG about video on OpenBSD, tomorrow. Go, if you are near.
It’s supported, and given how well DragonFly supports SMP and the number of processors Zen 2 supports, it’s a no-brainer if you’re in the market for a new server.
This week’s material filled up fast. It’s vacation season in the northern hemisphere, so let’s see what next week brings…
A bumper crop this week!