Move some historical material from front page to history section so it doesn't get...
[ikiwiki.git] / index.mdwn
6e5b2f57 1## Ongoing DragonFly News
b043b812 2
066f5eec 3<div class="digestbox">
382e0c68 4News from the <a href="">DragonFly Digest</a>
bef9be4c 5<ul>
1590b99f 6<span class="digestcontent">[[!inline pages="internal(digest/*)" feeds="no" template="digestitem"]]</span>
bef9be4c 7</ul>
bef9be4c 8</div>
056a8490 11### 2.2.1 released - 27 April 2009
7a3a2ac3 12
32705764 13The [[new 2.2 release|release22]] includes [[Hammer|hammer]], a filesystem that includes instant crash recovery,
6e5b2f57 14multi-volume file systems, data integrity checking, fine grained history retention, and the ability to
15mirror data to other volumes. It has undergone extensive stress-testing and is considered production-ready!
b45421dc 16
6e5b2f57 17### Summer of Code participation
b45421dc 18
3a07f91e 19DragonFly participated in Google's [Summer of Code]( program. Sample code from the completed student projects is available [from Google's repository](
b45421dc 20
b45421dc 21
6e5b2f57 22
23## What is DragonFly BSD?
b45421dc 24
25DragonFly belongs to the same class of operating system as BSD and Linux
26and is based on the same UNIX ideals and APIs. DragonFly gives the BSD
27base an opportunity to grow in an entirely different direction from the one
28taken in the FreeBSD, NetBSD, and OpenBSD series.
30From 2003 (when DragonFly first forked from FreeBSD), to early 2007,
31the DragonFly project focused on rewriting most of the major kernel
32subsystems to implement required abstractions and support mechanics
33for the second phase of the project. This involved a great deal of work
34in nearly every subsystem, particularly the filsystem APIs and kernel core.
35During all of this we have managed to keep the system updated with regards
36to the third party applications and base system utilities needed to make
37any system usable in production. We have also adopted the PkgSrc system for
38management of all non-base-system third-party applications in order to pool
39our resources with other BSD projects using the system.
41In the 2007-2008 time-frame a new filesystem called HAMMER was developed
42for DragonFly. HAMMER sees its first light of day in the July 2008
432.0 release. This filesystem has been designed to solve numerous issues
44and to add many new capabilities to DragonFly, such as fine-grained
45snapshots, instant crash recovery, and near real-time mirroring.
46The filesytem is also intended to serve as a basis for the clustering
47work that makes up the second phase of the project.
49The second phase of the project is now upon us. The DragonFly project's
50ultimate goal is to provide native clustering support in the kernel.
51This involves the creation of a sophisticated cache management
52framework for filesystem namespaces, file spaces, and VM spaces, which
53allows heavily interactive programs to run across multiple machines with
54cache coherency fully guaranteed in all respects. This also involves being
55able to chop up resources, including the cpu by way of a controlled VM
56context, for safe assignment to unsecured third-party clusters over the
57internet (though the security of such clusters itself might be in doubt,
58the first and most important thing is for systems donating resources to not
59be made vulnerable through their donation).
b043b812 60
b043b812 61
bef9be4c 62
473fa66e 63