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…
tmux post fixed
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.
tmux port redo
If you’re upgrading to the latest dports, and you use tmux – don’t update that particular port yet.
New quarterly packages available
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.)
hocus pocus in the dmesg
Yep, it’s probably there depending on your chipset.
Bounty paid for NVMM
I didn’t realize this, but there was a bounty offer for porting a hypervisor to DragonFly, listed on the DragonFly Code Bounties page. Aaron LI did it, and now he’s promptly paid, too. Put your name on a bounty if you’re willing and interested in paying.
NVMM in DragonFly, the story
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.
Low space and HAMMER2 snapshots
It used to be that if you had a HAMMER2 volume and ran low on space, snapshotting would stop so that you didn’t completely fill the disk. Now, thanks to Francis GUDIN, snapshots continue to roll forward and discard older ones to keep disk usage constant. It won’t fix the low disk space issue, but snapshots will stay up to date. It’s in 6.0 too.
NVMM, qemu, and dports
I think from this commit that qemu in dports is able to build NVMM-compatible. It won’t be in the current binaries for download because those are built from quarterlies, but work from source.
I am not sure those sentences I just typed would be comprehensible to a non-BSD user.
Radeons and accelerated graphics
Apparently a commit that I can’t find (“e8de9e9“?) disabled acceleration for R5 240 Radeon cards, but causes an error for R7 models. If you’ve got an R5 and you want accelerated video, try taking it out – assuming it’s not working already. Any other Radeon model, it may not make a difference.
Update: Pierre Alain-TORET found the correct commit.
passwdqc added to DragonFly
If you think about the name, you’ll realize what it does: libpasswdqc(8) does quality checks on passwords via PAM, and now it’s in DragonFly.
NVMM for DragonFly HOWTO
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.
How to mess up mail delivery
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 justin@shiningsilence.com 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.
Minor boot code move
boot and libstand directories are moved to src/stand/boot on DragonFly. This won’t affect most people, as you’ll upgrade and build the same way as always, but if you were specifically looking for it in the old locations of sys/boot and lib/libstand, you’d be surprised.
*_show_badconfig on by default in DragonFly
I didn’t know about this, but there’s a daily/weekly/monthly/security_show_badconfig option in periodic.conf that is now defaulting to “yes” in DragonFly. This I assume means you’ll get the output of erroring periodic scripts sent to you. Useful, especially if you find out about an error you hadn’t seen before.
covid(1) in DragonFly
ndis removed from DragonFly
ndis(4) is removed from DragonFly; it’s probably been years since it was applicable to any hardware. I don’t think it will affect anyone – but it’s an interesting tool from a historical perspective; for a while it was possible to use Windows XP drivers to create a BSD network driver, effectively.
Sometimes it really is bad RAM
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.
How big is chromium?
Here’s a link to a commit for dsynth that gives an idea of how huge a debug build of chromium can be.
Working Wireguard on DragonFly
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.