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.
Prompted by this email, I’ll say if there’s a DragonFly code bounty that interests you, put your name on it. Payment is on completion.
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.
LibreSSL in DragonFly has had a minor update, from 3.2.3 to 3.2.4, thanks to Daniel Fojt. It’s a bugfix update, but I’m using it as a chance to remind everyone you can use LibreSSL for everything in dports, too.
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.
Because there’s a newer version of sh(1) in DragonFly, you may need to update your 5.8 system to continue building ports from source. Binary installation through pkg still works as expected so this may not affect you.
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.
POSIX is a sort of standard for UNIX maintained by the IEEE. Most UNIX-ish systems implement it to some extent, though I am not sure to what degree. There’s an open source version of the standard, and Aaron LI made nanosleep match up.
If you edit /etc/fstab, and then later change something like the proc filesystem from OpenJDK, you might not boot normally. Antonio Olivares has a solution for you.
I always thought IRC was pretty decentralized, but I didn’t realize talk(1) was designed to work machine-to-machine. That means in theory that if you have a talk(1) binary on your machine, you could chat directly to anyone else with the same binary, even on a different platform. Since 4.3BSD! Anyway, I only realized this because of this recent bugfix thanks to Dan Cross.
The short answer is: works great. The version in dports lags, cause it’s based on what’s in the FreeBSD package collection, and that’s not updated as quickly.
This is technically the prerelease, since the official one is a few months off. TeX Live binaries can be downloaded directly for DragonFly.
This happened a little bit ago but I wanted to be able to post a solution to the pkg upgrade issue (yesterday) before mentioning it: there’s a freshly built batch of packages for DragonFly, so now is a good time to upgrade with pkg.
If you upgrade pkg on your system, it may start erroring out. This is because the default config will confuse the newer version. To fix this, you can copy over a working config and the problem will go away. I expect this may only be a problem until the next release.
MAP_VPAGETABLE has been removed in DragonFly because of conflicts with recent pmap work. This has the unfortunate effect of breaking vkernel(7), but vkernels can be resurrected with changes to use hardware virtualization support.
Note that running DragonFly as a VM is unaffected; that’ll still work just fine. This breakage is DragonFly-vkernel-on-DragonFly specific.
Aaron LI has ported timeout(1) to DragonFly. It’s a way to run a command with a time limit, and I’m happy to say it is a cross-BSD item, coming from NetBSD by way of FreeBSD.