If you are one of those unlucky/foolhardy people running DragonFly with very little RAM, this maxvnodes change will help you out.
(DragonFly is not that RAM-hungry in normal circumstances, anyway; 1-2G is ‘safe’, last I knew.)
James Cook continues to work on zalloc, and he’s published a small report on his progress.
I’ve seen this a number of times over the years: if you’re installing DragonFly and the install drive seems to disappear, it might be the USB port you plug into.
If you are upgrading an older 5.8.x system to DragonFly 6, and get a lua error when updating pkg: manually copy over a config file, and you’ll be set.
There’s only been one issue found in the release candidate so far. It’s fixed, so I’ll tag and build 6.0 within the next few days.
With good timing, 6.x packages are now available for those of you who need them.
Since DragonFly 6.x is a major number change, there’s no prebuilt packages that match that release number. As of this writing, the mirror master site shows 5.10 packages, which would work… if that was the next release. That’s where the number change trips it up. There should be new 6.x packages in the next few days. (Thanks to Jan Peter Vogt for the reminder)
The image should be at your nearest mirrors now.
The first RC for DragonFly 6.0 is branched. I don’t expect a need for a second one; this release has been a long time baking (look at the commit list!) and is pretty well refined.
I’ll be working on branching and releasing DragonFly 6.0 over the next while. We’re overdue for a release. Tentatively, I’ll branch tomorrow night, and start working on test images and release notes. The release will come in about a week, if there’s no surprises.
There’s a new build of binary packages available, for both 5.8 and DragonFly-current.