| 1 | ## Ongoing DragonFly News |
| 2 | |
| 3 | ### 2.2.1 released - 27 April 2009 |
| 4 | |
| 5 | The [[new 2.2 release|release22]] includes [[Hammer|hammer]], a filesystem that includes instant crash recovery, |
| 6 | multi-volume file systems, data integrity checking, fine grained history retention, and the ability to |
| 7 | mirror data to other volumes. It has undergone extensive stress-testing and is considered production-ready! |
| 8 | |
| 9 | ### Summer of Code participation |
| 10 | |
| 11 | DragonFly [has been accepted](http://socghop.appspot.com/org/home/google/gsoc2009/dragonflybsd) to Google's Summer of Code for 2009, after a successful [[2008 session|docs/developer/GoogleSoC2008]]. If you're a student, start planning for entering your proposal on the 23rd. If you can mentor, please sign up at the [Google site](http://socghop.appspot.com/) and request a mentoring slot. There is [[an initial page|gsoc2009]] listing potential projects; please read and add to it if you are interested. |
| 12 | |
| 13 | Check the [DragonFly Digest](http://www.shiningsilence.com/dbsdlog/) for other current events. |
| 14 | |
| 15 | |
| 16 | ## What is DragonFly BSD? |
| 17 | |
| 18 | DragonFly belongs to the same class of operating system as BSD and Linux |
| 19 | and is based on the same UNIX ideals and APIs. DragonFly gives the BSD |
| 20 | base an opportunity to grow in an entirely different direction from the one |
| 21 | taken in the FreeBSD, NetBSD, and OpenBSD series. |
| 22 | |
| 23 | From 2003 (when DragonFly first forked from FreeBSD), to early 2007, |
| 24 | the DragonFly project focused on rewriting most of the major kernel |
| 25 | subsystems to implement required abstractions and support mechanics |
| 26 | for the second phase of the project. This involved a great deal of work |
| 27 | in nearly every subsystem, particularly the filsystem APIs and kernel core. |
| 28 | During all of this we have managed to keep the system updated with regards |
| 29 | to the third party applications and base system utilities needed to make |
| 30 | any system usable in production. We have also adopted the PkgSrc system for |
| 31 | management of all non-base-system third-party applications in order to pool |
| 32 | our resources with other BSD projects using the system. |
| 33 | |
| 34 | In the 2007-2008 time-frame a new filesystem called HAMMER was developed |
| 35 | for DragonFly. HAMMER sees its first light of day in the July 2008 |
| 36 | 2.0 release. This filesystem has been designed to solve numerous issues |
| 37 | and to add many new capabilities to DragonFly, such as fine-grained |
| 38 | snapshots, instant crash recovery, and near real-time mirroring. |
| 39 | The filesytem is also intended to serve as a basis for the clustering |
| 40 | work that makes up the second phase of the project. |
| 41 | |
| 42 | The second phase of the project is now upon us. The DragonFly project's |
| 43 | ultimate goal is to provide native clustering support in the kernel. |
| 44 | This involves the creation of a sophisticated cache management |
| 45 | framework for filesystem namespaces, file spaces, and VM spaces, which |
| 46 | allows heavily interactive programs to run across multiple machines with |
| 47 | cache coherency fully guaranteed in all respects. This also involves being |
| 48 | able to chop up resources, including the cpu by way of a controlled VM |
| 49 | context, for safe assignment to unsecured third-party clusters over the |
| 50 | internet (though the security of such clusters itself might be in doubt, |
| 51 | the first and most important thing is for systems donating resources to not |
| 52 | be made vulnerable through their donation). |
| 53 | |
| 54 | [[!aggregate name="DragonFly Digest news" dir="digest" |
| 55 | feedurl="http://www.shiningsilence.com/dbsdlog/feed" |
| 56 | url="http://www.shiningsilence.com/dbsdlog/" updateinterval="1" |
| 57 | expireage="7" expirecount="20" template="digestpost"]] |
| 58 | |
| 59 | [[!inline pages="internal(digest/*)" feeds="no" template="inlinepage"]] |
| 60 | |