A running description of activity related to DragonFly BSD.
I’ve waited to post this because it’s a bit complicated, but here is the summary: dports didn’t get updated with new binary builds for a while because Rust stopped working, which killed Firefox. Michael Neumann got Rust working again, and packages are updated.
(Use -f if you have upgrade troubles.)
Your midweek short read: A “Putting DragonFly on a desktop machine” story that would incidentally work as an informal installation guide.
User am_dxer is using DragonFly, blind, with Orca. I didn’t know if it was possible, but this person proved it can be done. (and that’s an achievement worth supporting.)
If you have any local-only branches in your DragonFly git repo, you will need to apply this quick fix.
If you are interested in AES-GCM, and didn’t have to look it up on Wikipedia, and could implement it in the aesni(4) module – tell Sepherosa Ziehau.
BSDNow has reached the magic 200 episode mark, and this week they cover a nice wide range of topics – including Illumos!
If you happen to get missing shared library errors when running something installed via dports, you may have installed during a short period where this previously mentioned bug had bit. The fix is to replace with known good binaries, completely.
Should you need have Ubiquiti devices, and you need to get the Unifi management program running on your DragonFly server, this script will work for you. Some of the filepaths are different, but it’s otherwise complete.
No interview in this week’s BSDNow, but there’s a good run through recent BSD news, including some talk about a “Aeronix” machine project, which led me to some other interesting links.
Matthew Dillon noted some OpenVPN problems, requiring him to disable compression. I don’t think this is a DragonFly problem, or even necessarily a BSD problem, but it’s worth mentioning in case you run it.
Andrew MacIntyre manually installed DragonFly onto a UEFI system, and conveniently he posted his notes. It includes a GRUB menu entry, which will come in handy for someone
There’s a bug with shared libraries in pkg(), which may bite you when upgrading. It’s present in version 1.10.1 at least, so you may want to wait for this fix to be applied before your next upgrade.
This week’s BSDNow covers different topics, with a specific link about a centrally managed Bhyve – a new feature to me. No interview this week, but don’t let that stop you from the full range of discussion.
It’s always nice to see this out of nowhere: How to Install DragonFly BSD 4.6 + Xfce Desktop + Apps on VMware.
If you are using bhyve, and you want DragonFly on there as a ‘guest’ (not sure if that’s the right term), there’s a template available. (via)
DragonFly 4.8 is officially released! Download from your nearest mirror, where it should appear in the next 24 hours. If you’re upgrading your existing install, you can use the generic instructions in the release notes or in my users@ email; whichever you click first. Don’t forget to ‘pkg upgrade’!
An article about a semctl(2) bug on DragonFly, “Make DragonFlyBSD great again!“, has popped up a few times, in comments here, some online forums, and in IRC. I’m linking to it so that I can also say: read all the way to the end and notice the date. The bug was fixed more than 6 months ago. This is not a current security problem, but a (enjoyable) description of how someone in Poland documented it.
Nobody reads anything but headlines, geez.
The last time SSH was updated in DragonFly, a DragonFly-specific customization, “PasswordAuthentication No”, was reverted to the default. This meant password logins through SSH worked on DragonFly – which is normal for perhaps every other UNIX-ish operating system, but DragonFly has traditionally defaulted to requiring a key out-of-the-box.
It has been fixed, and you can change the setting back. This only affected DragonFly-master from August through March. 4.6 users are unaffected.