| | 1 | # Ongoing DragonFly News |
| | 2 | |
| | 3 | Check the [DragonFly Digest](http://www.shiningsilence.com/dbsdlog/) for current events. |
| | 4 | |
| | 5 | DragonFly's new HAMMER filesystem is fast becoming a mainstay of the |
| | 6 | system, with numerous people now using it on production machines! |
| | 7 | The release of the new filesystem in 2.0 has gone very smoothly with |
| | 8 | only minor bugs reported to date! |
| | 9 | |
| | 10 | |
| | 11 | # DragonFly-2.2 RELEASED February 2009!! |
| | 12 | ## 2.2.0 - 17 February 2009 |
| | 13 | |
| | 14 | The **[[DragonFly-2.2.0 Release|release22]]** |
| | 15 | is ready! |
| | 16 | |
| | 17 | # What is DragonFly BSD? |
| | 18 | |
| | 19 | DragonFly belongs to the same class of operating system as BSD and Linux |
| | 20 | and is based on the same UNIX ideals and APIs. DragonFly gives the BSD |
| | 21 | base an opportunity to grow in an entirely different direction from the one |
| | 22 | taken in the FreeBSD, NetBSD, and OpenBSD series. |
| | 23 | |
| | 24 | From 2003 (when DragonFly first forked from FreeBSD), to early 2007, |
| | 25 | the DragonFly project focused on rewriting most of the major kernel |
| | 26 | subsystems to implement required abstractions and support mechanics |
| | 27 | for the second phase of the project. This involved a great deal of work |
| | 28 | in nearly every subsystem, particularly the filsystem APIs and kernel core. |
| | 29 | During all of this we have managed to keep the system updated with regards |
| | 30 | to the third party applications and base system utilities needed to make |
| | 31 | any system usable in production. We have also adopted the PkgSrc system for |
| | 32 | management of all non-base-system third-party applications in order to pool |
| | 33 | our resources with other BSD projects using the system. |
| | 34 | |
| | 35 | In the 2007-2008 time-frame a new filesystem called HAMMER was developed |
| | 36 | for DragonFly. HAMMER sees its first light of day in the July 2008 |
| | 37 | 2.0 release. This filesystem has been designed to solve numerous issues |
| | 38 | and to add many new capabilities to DragonFly, such as fine-grained |
| | 39 | snapshots, instant crash recovery, and near real-time mirroring. |
| | 40 | The filesytem is also intended to serve as a basis for the clustering |
| | 41 | work that makes up the second phase of the project. |
| | 42 | |
| | 43 | The second phase of the project is now upon us. The DragonFly project's |
| | 44 | ultimate goal is to provide native clustering support in the kernel. |
| | 45 | This involves the creation of a sophisticated cache management |
| | 46 | framework for filesystem namespaces, file spaces, and VM spaces, which |
| | 47 | allows heavily interactive programs to run across multiple machines with |
| | 48 | cache coherency fully guaranteed in all respects. This also involves being |
| | 49 | able to chop up resources, including the cpu by way of a controlled VM |
| | 50 | context, for safe assignment to unsecured third-party clusters over the |
| | 51 | internet (though the security of such clusters itself might be in doubt, |
| | 52 | the first and most important thing is for systems donating resources to not |
| | 53 | be made vulnerable through their donation). |
| | 54 | |
| | 55 | |
projects / ikiwiki.git / blame_incremental