On May 10th, the DragonflyBSD team released version 6.0. Let’s take a look at what changes make up this release.
For those of you who are not aware of what DragonflyBSD is, let me enlighten you. The DragonflyBSD project began in 2004. It was created by Matthew Dillon after a falling out with the FreeBSD developers. Dillon disagreed with the development path they chose for FreeBSD 5, so he forked FreeBSD 4.
One of the biggest changes made to DragonflyBSD was an overhaul of the kernel. This included “inter-process communication via message passing.” Many of the changes were inspired by Dillon’s work on Amiga. “The Amiga kernel was designed around small but powerful APIs and messaging. Having a small, well defined API for a subsystem results in fewer bugs, easier to find bugs, and code sustainability.”
Another feature that sets DragonflyBSD apart is the fact that it has its own file system. HAMMER is designed to be a Unix File System (or UFS) replacement. UFS is a descendant of the original Unix file systems and is used in many BSDs. HAMMER has similar features to ZFS, including “instant crash recovery, multi-volume file systems, integrity checking, fine grained history/undo, networked mirroring, and historical snapshots”. HAMMER2 is the current version.
Changes in DragonflyBSD 6.0
Here are a list of the changes that have been made for the 6.0 release:
- Significant work was done on dsynth, which is used for building packages
- HAMMER2 received multiple cleanups and fixes. It also received initial multi-volume support.
- non-GPL ext2 filesystem support added.
- Meltdown hardware is detected during boot on Intel.
- amdsmn imported from FreeBSD
- Support added for newer Intel I219 Ethernet controllers.
- Multiple updates and stability fixes to the i915 driver.
- DRM system now matches Linux 4.10.17.
- GCC 8 now set as default.
- A full set of new binary packages has been built for 6.0
- Improved EFI framebuffer support
- Significant performance enhancements for TMPFS