The recent tmux package update reminds me to mention ‘pkg lock’. When you update packages, pkg will update everything. If there’s a package you don’t want changed, the pkg lock(8) command will keep it at the current version. There can be some other packages held back because of dependencies, but that’s OK. Don’t forget to pkg unlock when no longer needed…
NYCBUG’s hosting “Extreme scripting with KSH and AWK” with G Clifford Williams, tomorrow. It’s online, so everyone can get the lesson.
If you want to update to the now fixed tmux port, you’ll want to add a -f to the pkg command to force it; the version number hasn’t changed.
tuxillo has built a new set of packages for dports; upgrade using the instructions in his post. (Though ‘pkg upgrade’ has generally worked for me as the quickest solution.)
Aaron LI posted a summary of how he went from zero to done, so to speak, porting NVMM to DragonFly. There’s some interesting future projects there, too.
The headline says almost everything, in this case. There’s a HOWTO for DragonFly NVMM which should get most of what you want to do, and I’m sure it will be updated.
Here’s something I just learned: If you are running dma(8), /etc/dma.conf will contain MAILNAME. If your email server is somewhere else, but you set MAILNAME as your domain – dma will deliver locally.
I had /etc/dma.conf set with MAILNAME shiningsilence.com – so dma kept delivering overnight periodic results to root, which was aliased to firstname.lastname@example.org in /etc/mail/aliases and so it was delivered to ‘justin’ locally on the machine.
Changing MAILNAME to www.shiningsilence.com – the host you are reading right now – fixed the problem. Now, whether this was an automatically set config or something I misconfigured some years ago… I can’t tell.
The version of qemu in dports is not set up to support this, yet. Until then, you can download a prebuilt version.
ChiBUG meeting is at 6 PM at the normal place, which means you should go if you are near, and vaccinated.
Many, many times over the years I have tried answering problems with “… and maybe something’s wrong with the RAM?”, which is always possible but not always probable. For once, it’s really what happened in this story of strange HAMMER2 errors.
This note from James Cook describes how to get Wireguard functioning on DragonFly; his linked patch is not necessary at this point since it’s been committed to dports – though not in the latest binaries.
I’m actually some days late in reporting this, but there’s a new full build of packages for DragonFly 6.0; it’s following the quarterly release schedule for ports, so 2021Q2 is the base.
This goes with the recent merges from -current into 6.0. Now is a good time to update your system completely, if you have not already.
James Cook continues to work on zalloc, and he’s published a small report on his progress.
If you are upgrading an older 5.8.x system to DragonFly 6, and get a lua error when updating pkg: manually copy over a config file, and you’ll be set.