Matt Dillon disagreed with FreeBSD 5's threading direction. Built HAMMER filesystem and unique SMP approach.
DragonFly BSD is a Unix-like operating system forked from FreeBSD 4.8. Its key innovations include a lightweight kernel threading system using message-passing rather than fine-grained locking for SMP, the HAMMER and HAMMER2 filesystems with built-in snapshotting and replication, and a virtual kernel facility for running kernels in userspace.
Matt Dillon was not your average FreeBSD contributor. An Amiga developer in the late 1980s and a FreeBSD committer since 1994, he had strong opinions about operating system design—particularly about how to handle symmetric multiprocessing (SMP). When FreeBSD 5.x adopted a fine-grained locking approach inspired by traditional Unix SMP designs, Dillon was convinced it was the wrong path: too complex, too fragile, and destined to create maintenance nightmares.
Dillon tried to push his alternative vision within FreeBSD, advocating for a message-passing architecture that would make SMP more manageable. The disagreements grew heated. Other FreeBSD developers weren't buying what he was selling, and eventually his commit access was revoked. It wasn't a personality clash so much as a fundamental architectural disagreement—two irreconcilable visions of how a kernel should handle modern hardware.
In June 2003, Dillon forked FreeBSD 4.8 and announced DragonFly BSD on the FreeBSD mailing lists on July 16. He initially described it as 'the logical continuation of the FreeBSD 4.x series,' positioning it as the road not taken. The project attracted a small but dedicated community of developers who shared his vision.
DragonFly's most significant technical achievement is the HAMMER filesystem, a 64-bit filesystem featuring infinite snapshots, master-slave replication, checksumming, and fsck-less mounting. HAMMER was declared production-ready in 2009, and its successor HAMMER2 became stable in 2018. These innovations proved that Dillon's instincts about OS design, while unconventional, produced genuinely novel results.
Notably, despite the acrimonious split, DragonFly BSD and FreeBSD maintain a cooperative relationship, sharing bug fixes, driver updates, and improvements. It's one of the more civil post-fork relationships in the BSD world.
Matt Dillon begins contributing to FreeBSD
Dillon forks FreeBSD 4.8 to start DragonFly BSD
DragonFly BSD announced on FreeBSD mailing lists
DragonFly BSD 1.0 released
HAMMER filesystem declared production-ready with DragonFly 2.2
HAMMER2 filesystem declared stable with DragonFly 5.2
DragonFly BSD remains a niche operating system, but its technical contributions have been significant. The HAMMER filesystem influenced thinking about filesystem design, and Dillon's message-passing approach to SMP provided a useful counterpoint to the dominant fine-grained locking paradigm. Some of FreeBSD 5.x's SMP issues validated Dillon's concerns, even if the project eventually worked through them.
The fork also demonstrated that BSDs can coexist and collaborate even after splitting. The BSD ecosystem's culture of sharing code across projects meant that DragonFly's innovations could benefit the broader community.