I didn’t know this, but the label in disklabel(8) is called “pack ID” in the man page, and there’s only one way to update it right now in DragonFly. You may only need to know this a few times in your life.
Something I didn’t know but also never tried: ttyv0, the base terminal when booting up DragonFly, can extend to a max of 160 characters. Given that I am used to 80, that seems like overkill.
As part of installing DragonFly, Jonathan Engwall happened to create a script to install every part of xfce4 that he wanted. I’m linking to it in case you want it too.
(xorg and web browser install not included)
For those with a different keyboard layout – different than US English, I mean – and running xorg 1.20 or later: setxkbmap is the command you need.
If you have an AMD processor, support for the System Management Network and CPU temperature readings are now available in DragonFly as amdsmn(4) and amdtemp(4).
Instead of posting about updates, here’s a feature that you will hopefully never notice: ‘make upgrade’, part of the upgrade process in DragonFly, will now go look for 3rd party software built to depend on deprecated DragonFly system libraries, before removing those libraries. (details) If you’ve had a program stop running because something else was upgraded – and I’m sure you have, cause “dll hell” is an actual phrase – you’ll be thankful for this.
For those of you who like csh, or are too lazy to switch away from it, it now includes the current directory in the prompt on DragonFly. Another of those “hey, this can still get updates?” moments for me.
If you’re running a very recent HP laptop, this recent DMAP change may get DragonFly to boot on it.
EDIT: this MSIX fix, too.
DragonFly’s direct rendering has been updated to match Linux 4.12.15, which means improved support for a number of Intel processors.
If you have an Intel-based system and it has trouble reading some USB ports, or odd behavior with some virtual machines, this recent bugfix in DragonFly-current may help you. I know, my description is vague, but I haven’t encountered this directly.
It’s odd to think this, but the process of swapping out something entirely from RAM perhaps doesn’t really apply any more (except for compatibility).
A note for the future: if pkg itself isn’t working, you can use pkg-static.
In Daniel Fojt’s ongoing series of third-party software upgrades, he’s moved libreSSL in DragonFly up a major version, from 2.9.1 to 3.1.3. This includes TLS 1.3, among other features.
Well, it’s really the meltdown fix for Intel. You now will see it noted if the fix is present, during the DragonFly boot process.
Tomohiro Kusumi has imported a new version of ext2 filesystem support into DragonFly.
Thanks to Daniel Fojt, ldns in DragonFly is updated to 1.7.1. This time, I do have a changelog link.
It’s a minor update, but I have to point it out because my muscle memory still won’t let go of nslookup,
Francois Tigeot has updated the DRM driver in DragonFly to match what’s in Linux kernel 4.10.17. What’s that change? A few minutes of poking about doesn’t find a granular enough changelog.
Not Direct Memory Access, but the DragonFly Mail Agent, born from a desire to replace larger mail transfer agents. It has its own repository, and the upgrade came from there back into DragonFly.