The first RC for DragonFly 6.0 is branched. I don’t expect a need for a second one; this release has been a long time baking (look at the commit list!) and is pretty well refined.
I’ll be working on branching and releasing DragonFly 6.0 over the next while. We’re overdue for a release. Tentatively, I’ll branch tomorrow night, and start working on test images and release notes. The release will come in about a week, if there’s no surprises.
There’s a new build of binary packages available, for both 5.8 and DragonFly-current.
Thanks to Levente Kurusa and Aaron LI, pkill(1) now has a -T option, to limit the killed processes to the current terminal. It’s a minor change, but worth remarking cause if you are killing multiple processes, your muscle memory is going to take over.
I am not sure if these Radeon cards are tested on DragonFly, but it’s a good base to start from.
I was sure I had posted a link to this before, but apparently not: “How to install DragonFly BSD 5.6.1 plus MATE and some aplications” (Youtube, via)
New to me, at least, on the DragonFly images page.
If you’re running on DragonFly master, make sure you are on the right version of bmake. If you are on 5.8, it won’t affect you.
Well, that’s not exactly correct: you can mount more than one tmpfs, and you can mount multiples at the same spot, but I can’t think of a reason to do so. In fact, it could happen by accident, but there’s a fix for that in DragonFly, thanks to Aaron LI. Not a major problem, but mentioning it in case you saw it and were confused.
There’s a new build of DragonFly 5.8 binary packages available. There’s a sudo fix in there for the recent public cross-platform CVE it had, plus the linked announcement describes how to get around a pkg upgrade bug.
I’m not sure if this is directly helpful, but a recent series of posts about running jitsi on DragonFly covers the different parts of setting it up. There isn’t a “this is the solved answer” post to point at; I’m linking to the start of the thread as it might be useful for someone.