You can now create FAT volumes on DragonFly. Not exactly high-tech, but a filesystem that most anything can read and write.
6.0.1 is tagged and available. The major reason for this update is an expired Let’s Encrypt certificate that would cause problems when downloading dpkg binaries. A list of 6.0.1 commits is available.
I recommend the usual rebuild process mentioned on the 6.0 release notes:
make buildworld
make buildkernel
make installkernel
make installworld
make upgradeDon’t forget to update your packages with ‘pkg upgrade’.
If you have encountered that problem with Let’s Encrypt and dports, the fix is committed and a make world is needed.
If libvirt running with nvmm on DragonFly interests you, watch this bug report.
You may get some errors because of an expiring base Let’s Encrypt certificate when using pkg. It’s being worked on.
The not-official-but-still-used mirror-eu-1.dragonflybsd.org mirror is going away later next month. The main site probably has enough bandwidth to compensate.
Not huge news about mandoc, but I always like linking to updates with clear changelists.
I installed new SSL certificates for this server over the weekend and I have to say, Let’s Encrypt and certbot are the easiest SSL setup process I’ve ever done. It worked exactly as expected on DragonFly.
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…
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.
If you’re upgrading to the latest dports, and you use tmux – don’t update that particular port yet.
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.)
Yep, it’s probably there depending on your chipset.
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.
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.
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.
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.
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.
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.