Alexandre Perrin contributed an upgrade of wpa_supplicant and hostapd for DragonFly, bringing it from 0.6.10 to version 2.1 – a 4-year jump.
Thanks to John Marino and people I don’t know the name of in the gcc project, DragonFly is now part of the gcc test suite.
“What about clang?” you say? We’re not picky; DragonFly works with either.
I’ve branched DragonFly 3.8, and tagged a release candidate. Please try the release candidate if you can. I have links in my post to users@/kernel@. Don’t forget the remaining issues! Planned release date is June 4th.
The slides from Francois Tigeot’s talk about benchmarking DragonFly with PostgreSQL are now online – link is to a PDF.
The May BSD Magazine is out, and Siju George has written an article about using Hammer on DragonFly. It’s a free download to read.
(link fixed)
We’re due for the next release of DragonFly. I’ve posted the two-week warning to kernel@. As I noted in that post, please look at the list of issues for the release and see what you can close.
Francois Tigeot is giving a talk tomorrow on benchmarking DragonFly using PostgreSQL, at PGCon 2014. PGCon is the PostgreSQL convention happening immediately after BSDCan in the same location, in case you didn’t know already.
Imre Vadasz is our newest DragonFly committer. Welcome, Imre!
Portmaster, if you install it, tells you to upgrade your packages. If you are on DragonFly, you are already upgraded.
Sepherosa Ziehau has enabled GSI target CPU auto selection, by default, on x86_64. He says to let him know if there’s problems. I’m not sure what form the problems would take, cause I’m not sure what this does.
Matthew Dillon brought in Adrian Chadd’s sleep state changes for the ath(4) driver from FreeBSD to DragonFly; you may see reduced power usage if you have the appropriate hardware.
libpcap has been updated in DragonFly by Matthew Dillon, and file has been updated by Peter Avalos.
I’ve seen Atlassian Confluence, a Java-based wiki program, in a few places. Atlassian apparently offers their software at a discount (free?) to qualified open source projects. I set up Confluence 5.4 on DragonFly as a test run, and it generally worked. That’s great! I tried to set up version 5.5, and it will not start.
May 08, 2014 7:24:41 PM org.apache.catalina.core.ContainerBase startInternal
SEVERE: A child container failed during start
java.util.concurrent.ExecutionException: java.lang.InternalError: platform not recognized
at java.util.concurrent.FutureTask.report(FutureTask.java:122)
This is annoying. DragonFly (or any BSD) is not supported by Atlassian for Confluence, so it’s not a surprise… but I was so close! Their product has a very nice interface and I was planning to replace Mediawiki at my workplace with it, for some internal documentation. This FreeBSD bug report is the closest fix I can find, but it’s old enough it shouldn’t matter now.
Wojciech Puchar noted with some surprise that DragonFly uses less CPU than expected for high-packet-rate traffic. This has been going on for a while, and apparently Sepherosa Ziehau has even more improvements planned.
The reaction I have heard a number of times from new DragonFly users: hey, this runs really fast, even when I try to load it down!
ATM support is gone in DragonFly, and frankly, I’m surprised it was still there.
Sascha Wildner’s updated ACPICA to version 20140424. Will that help you? Perhaps with newer motherboards; otherwise check the changelog.
The pkg tool, used in DragonFly (and FreeBSD) for ports, is at version 1.2. Version 1.3 will apparently be able to solve the problem where one port is ended and replaced with another. This is a problem that’s been around forever, and I don’t just mean with pkg. I don’t know how soon 1.3 will be out, or what version FreeBSD is at.
Just so nobody’s surprised: DragonFly process IDs now go an order of magnitude higher.