DragonFly 3.4 released!

As posted in my email to users@: Version 3.4 of DragonFly is officially out.

The release ISO/IMG files are all available at the usual mirrors:


The release notes have details on all the changes:


If you are planning to try the new dports system for installing third-party software, check the DPorts Howto page:


If you have an installed DragonFly 3.2 system and you are looking to upgrade, these (not directly tested) steps should work, as root:

cd /usr/src
git fetch origin
git branch DragonFly_RELEASE_3_4 origin/DragonFly_RELEASE_3_4
git checkout DragonFly_RELEASE_3_4

… And then go through the normal buildworld/buildkernel process found in /usr/src/UPDATING.  If you are running a generic kernel, that can be as simple as

make buildworld && make buildkernel && make installkernel && make installworld && make upgrade

(and then reboot)

If you encounter problems, please report them at bugs.dragonflybsd.org.  I get better at testing for each release, but I also get better at discovering new problems just after release.

Mailing lists interruption

There’s an as-yet-undiagnosed problem with the @dragonflybsd.org mailing lists; you won’t see any mail from them right now.  I don’t have an ETA for a fix because I don’t know the underlying cause yet…

Update: Fixed; I think – dragonflybsd.org DNS server was not responding, and it had a ripple effect.

Binary package removal for DragonFly 2.11 and below

On the 10th of November, I’m going to remove the binary pkgsrc packages from mirror-master.dragonflybsd.org for DragonFly 2.8 through 2.11.  They are closing in on 2 years old at this point, and are from a pkgsrc branch that hasn’t been updated for that long.

If you are actually using version of DragonFly that old, you can continue building from pkgsrc normally; these are just prebuilt packages.

Holy crap, look at those numbers

Remember the new scheduler work?  Well, it continued, and now Francois Tigeot has posted pgbench benchmarks of the progress and benchmarks of DragonFly vs. other operating systems.  The links are to PDFs; scroll down as each have multiple pages.

The summary result: If you’re running Postgres, you probably want to do it on DragonFly.  The numbers are the best results for any BSD,  even better to some extent than Linux, which has had its own issues with schedulers and Postgres.  DragonFly 3.2 will include these improvements.

3.2 branch and release plan

As I typed elsewhere, my general plan is to branch DragonFly 3.2 on the 8th, and release on the 22nd.  That should give the recent scheduler and gcc work a chance to settle, and perhaps get a new version of USB support in too.  It will probably be using pkgsrc-2012Q3, also, though we may not have binary i386 packages.  3.2 is shaping up to be a much more significant release than I expected.