A writeup that may help someone in the future: if you decide you want to encrypt your /home directory, on DragonFly, this is how you do it.
Because of the major version number change, there’s no packages built for DragonFly 4.9. Your options are to either update to 5.1 (which you probably meant to do anyway if you are running current) or manually point to the newest packages. Or just build from dports.
For clarity, this does not affect you at all if you are running 5.0 release. It only affects you if you are running DragonFly-current and have not updated in a while.
Michael W. Lucas is talking tonight at SemiBUG’s monthly meeting, and will be presenting on Tarsnap. Go, if you are near Michigan.
DragonFly 5.0.0 has been released. HAMMER2 is available in the installer. Multi-volume/clustering support isn’t in there yet, but support for deduplication/snapshots/booting and so on all are. My post to users@ has upgrade instructions.
Here’s your heads-up: NYCBUG is having an TOR installation party tomorrow. Go, if you are near.
I tagged DragonFly 5.0 (commit message list in that link) over the weekend, and there’s a 5.0 release candidate for download. It’s RC2 because the recent Radeon changes had to be taken out.
BSDNow 213 talks about the just-finished EuroBSDCon, and vBSDCon and other things. The episode 213 web page links to Youtube videos of all the talks, so there’s your evening schedule, filled.
If you are starting KDE on DragonFly, you’ll want to be sure dbus is started too. Mentioning it juuuuuust in case…
HAMMER2 is now available by default in DragonFly, and can be used in the installation process. (It was possible, but manual, before.) The next DragonFly release should be soon.
Here’s a detailed writeup from Aaron LI on how to get a DragonFly system onto an IPv6 network.
Update: He also supplied an example pf ruleset that solved some IPv6 throughput problems for his VPS.
Pulled from a longer thread: x.x.1 update instructions for DragonFly.
Probably old hat to most readers, but I like to see this documented, and the hw.ncpu ‘trick’ is nice.
There will be a bootable, single-image version of HAMMER2 in the next DragonFly release. Matthew Dillon has a note about what will be in place at that point, and you can always look at the recent commits.
I should have linked this yesterday: a description of kcollect and its uses from Matthew Dillon, complete with example graph of a very busy machine.
The DragonFly Go builder needs a new maintainer, and an update to a newer builder. Are there any people out there interested in Go who want to do the work? I do not have time.
DragonFly 4.8 has been updated to 4.8.1, bringing in a lot of small fixes. Improved Intel video support and the virtio_scsi driver will be of most interest, I think. The 4.8.1 tag commit has all the details. You can update the normal way, and if you need an install image, I’ve uploaded them and they should appear at your local mirror.
Ján Su?an has posted some ideas about handling firmware in userland, in DragonFly. I’d like to see it happen.
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.