DragonFly 4.2 released
Version 4.2 of DragonFly brings significant updates to i915 and Radeon support, a move to GCC 5 (and the first BSD to do so), a replacement to Sendmail, and numerous other changes including OpenSSL updates, a new boot screen, improved sound, and improved USB support. 4.2.1 was released July 1st to fix a problem with Intel video chipsets. Version 4.2.2 was mis-tagged and immediately replaced by version 4.2.3 on July 13th, with a newer version of OpenSSL. Version 4.2.4 was rolled on August 9th to fix a rare error on shutdown.
- BSDTalk 255: a quick note
- HAMMER2 root mounts and live dedup too
- Lazy Reading for 2015/08/30
- In Other BSDs for 2015/08/29
- BSDNow 104: Beverly Hills 25519
- i915 support moves forward again
- Static site generator recommendations
- Many Hammer 1 updates, and credit
- More radeon updates
- True and False code reading, tonight
What is DragonFly BSD?
DragonFly belongs to the same class of operating systems as other BSD-derived systems and Linux. It is based on the same UNIX ideals and APIs and shares ancestor code with other BSD operating systems. DragonFly provides an opportunity for the BSD base to grow in an entirely different direction from the one taken in the FreeBSD, NetBSD, and OpenBSD series.
DragonFly includes many useful features that differentiate it from other operating systems in the same class.
The most prominent one is HAMMER, our modern high performance filesystem with built-in mirroring and historic access functionality.
Virtual kernels provide the ability to run a full-blown kernel as a user process for the purpose of managing resources or for accelerated kernel development and debugging.
The kernel makes extensive use of tokens as a synchronization mechanism; tokens are inherently deadlock-free and easily composable. The use of soft token locks results in less cross-subsystem pollution and more maintainable code, both of which allow us to parallelize the system with less effort compared to other kernels, which primarily use hard mutex locks.
DragonFly is uniquely positioned to take advantage of the wide availability of affordable Solid Storage Devices (SSDs), by making use of swap space to cache filesystem data and meta-data. This feature, commonly referred to as "swapcache", can give a significant boost to both server and workstation workloads, with a very minor hardware investment.
The DragonFly storage stack comprises robust AHCI drivers, stable device names via DEVFS and a partial implementation of Device Mapper for reliable volume management and encryption.
Some other features that are especially useful to system administrators are variant symlinks (i.e. symlinks that are resolved at runtime based on user-specific or system-wide variables) and a performant and scalable TMPFS implementation. Our system makes pervasive use of NULLFS mounts, which allow the administrator to make arbitrary parts of the filesystem hierarchy visible in other locations with virtually no overhead.
A major crux of any open source operating system is third party applications. DragonFly leverages the dports system to provide thousands of applications in source and binary forms. These features and more band together to make DragonFly a modern, useful, friendly and familiar UNIX-like operating system.
The DragonFly BSD community is made up of users and developers that take pride in an operating system that maintains challenging goals and ideals. This community has no reservation about cutting ties with legacy when it makes sense, preferring a pragmatic, no-nonsense approach to development of the system. The community also takes pride in its openness and innovative spirit, applying patience liberally and always trying to find a means to meet or exceed the performance of our competitors while maintaining our trademark algorithmic simplicity.
DragonFly provides a welcoming environment for those looking to participate in open source. See the Projects, Research Projects, Code Bounties and Summer of Code Projects pages for project ideas. If you are looking for an easy way to get your feet wet, you might find something suitable in the Bug Tracker. Or bring up your own idea on the appropriate mailing list or IRC!