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.
This week’s BSD Now talks about some pro-BSD ideas, which may or may not include the idea of Linux with a BSD userland. I find it slightly upsetting.
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.
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.
No mini-theme this week.
The one good use of social media: jokes on an obscure theme. (via)
No theme this week; just catching up with all the links I didn’t get to last week.
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.
This week’s BSD Now covers different topics – you may think from the headline it’s a “tips and tricks” link, but no, it’s about confidential info.
Aaron LI’s added NVMM, hardware acceleration for virtual machines, to DragonFly.
The version of qemu in dports is not set up to support this, yet. Until then, you can download a prebuilt version.
Since NVMM originated on NetBSD, the NetBSD documentation page for it describes how to use it quite well. There’s a man page in DragonFly for it too, of course. There’s even basic machines to try.
ChiBUG meeting is at 6 PM at the normal place, which means you should go if you are near, and vaccinated.
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.
More BUG meetings are happening, which is great.
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.
This week’s BSD Now goes into structure and progress, judging from the titles on display. Also, I did not link last week’s “410: OpenBSD Consumer Gateway” because I was on the road – look at it too if you haven’t yet.
covid(1), the program, from NetBSD and now in 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.
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.