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.
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.
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.
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.
I’m doing a catch-up post here to note all the smaller updates, some cross-BSD, that have gone into DragonFly in the last week or two: openresolv 3.12.0, dhcpcd 9.4.0, tzdata2020f, 802.11 channel definitions, stdbuf(1) and libstdbuf(3), sockaddr_snprintf(), and getaddrinfo(1).
You can’t tell directly from the commit message, but committing to DragonFly may trigger a reminder to MFC, based on commit message content. This is thanks to Aaron LI. It’s little, but this sort of automation is a good idea.
Aaron LI’s added a pw-update.sh script to DragonFly, for use in automating group and user changes, especially as – someday – part of a binary upgrade.
If you remember HAMMER1’s ability to create a volume that spanned multiple local disks, that capability’s been introduced to HAMMER2. Look at the commit message to see how it works so far.
Note that this is not multi-master replication.
DRM in DragonFly has been updated to match Linux 4.15.18, along with recognizing some new hardware.
This won’t affect your day-to-day operation of DragonFly, but it’s interesting: apparently, uptime was always (now minus boot time). If you reset the clock on the machine, however, it would no longer be accurate. Now it is accurate, for a number of utilties.
One last thing sneaking in for the week: There’s an update for libressl in DragonFly that fixes CVE-2020-1971. It’s there for 5.8 or -current.
Because of this commit that makes some changes to lib/stdio, you might get more reinstalls than you expect on your next pkg upgrade because of the __DragonFly_version change. This only applies to -current (5.9) users.
(I might be wrong)
If you want to build a kernel with no options, stripped down, here you go. I don’t know how useful it would be…
Matthew Dillon has made significant changes to the callout API in DragonFly. Interesting to look at, but I think no changes from a user point of view.
DragonFly has a new version of libressl, noting cause it has a newer TLS1.3 implementation – something that may be necessary for you.
There’s a minor update to dhcpcd in DragonFly, which may be of specific interest if you’re on an IPv4/IPv6 network – there’s a Preferred option added for that.
binutils and ld in DragonFly have been set to binutils234 and ld.bfd temporarily, for what appears to be work with the EFI bootloader. This should not make a difference for normal use; rebuilding binaries will give you different results but they’ll run.
cpdup(1) will now exactly recreate symlinks. That may be helpful for your backup strategy if it already involves cpdup.