In Other BSDs for 2014/12/13

Get ready for some reading.

Installworld, no matter what

It’s possible, if you are several releases (years) behind, to end up with a DragonFly system that can’t compile and install the current release, due to incremental changes over time.  It’s rare, but it could happen now between, say, version 3.4 and 4.0.  The usual solution would be to incrementally upgrade in order, which is a lot of building and updating.  The alternative is the new installworld-force option from Matthew Dillon that forces a new set of binaries into place.  Use as a last resort.

IPFW2 branch for testing

bycn82’s rewrite of IPFW2 is available as a git branch to try out; he’s posted the link.  Please try, especially if you are still working with the original ipfw.

(note: remember, ‘ipfw’ in DragonFly is what was called ‘ipfw2’ years and years ago because it was a replacement of the original ‘ipfw’ in FreeBSD.  It was called ipfw2 but referenced as ipfw so that the same commands worked.  Technically, this branch bycn82 is working on would be ipfw3, but he keeps referring to it as ipfw2.  Confused?  Good.)

In Other BSDs for 2014/12/06

I have been building up quite the variety this week.

A pile of DragonFly commits

In an effort to reduce my backlog of DragonFly things to post about, here’s quick notes:

DragonFly 4.0 released!

The 4.0 release of DragonFly is out!  Quoting from the release page:

Version 4 of DragonFly brings Haswell graphics support, 3D acceleration, and improved performance in extremely high-traffic networks. DragonFly now supports up to 256 CPUs, Haswell graphics (i915), concurrent pf operation, and a variety of other devices.

The more eagle-eyed downloader will notice it’s version 4.0.1, not 4.0.0.  That’s because nobody trusts .0 releases I tagged 4.0.0 just before a few useful commits went in, and it’s better to retag to make sure everyone got them.  See also my message to kernel@/users@