Changing headline CSS class
[ikiwiki.git] / index.mdwn
CommitLineData
6e5b2f57 1## Ongoing DragonFly News
b043b812 2
bef9be4c 3<div class="infobox">
382e0c68 4News from the <a href="http://www.shiningsilence.com/dbsdlog/">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>
9
10
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
c8354908 19DragonFly [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.
b45421dc 20
bef9be4c 21Check the [DragonFly Digest](http://www.shiningsilence.com/dbsdlog/) for other current events, or check the headlines listed on this page.
b45421dc 22
6e5b2f57 23
24## What is DragonFly BSD?
b45421dc 25
26DragonFly belongs to the same class of operating system as BSD and Linux
27and is based on the same UNIX ideals and APIs. DragonFly gives the BSD
28base an opportunity to grow in an entirely different direction from the one
29taken in the FreeBSD, NetBSD, and OpenBSD series.
30
31From 2003 (when DragonFly first forked from FreeBSD), to early 2007,
32the DragonFly project focused on rewriting most of the major kernel
33subsystems to implement required abstractions and support mechanics
34for the second phase of the project. This involved a great deal of work
35in nearly every subsystem, particularly the filsystem APIs and kernel core.
36During all of this we have managed to keep the system updated with regards
37to the third party applications and base system utilities needed to make
38any system usable in production. We have also adopted the PkgSrc system for
39management of all non-base-system third-party applications in order to pool
40our resources with other BSD projects using the system.
41
42In the 2007-2008 time-frame a new filesystem called HAMMER was developed
43for DragonFly. HAMMER sees its first light of day in the July 2008
442.0 release. This filesystem has been designed to solve numerous issues
45and to add many new capabilities to DragonFly, such as fine-grained
46snapshots, instant crash recovery, and near real-time mirroring.
47The filesytem is also intended to serve as a basis for the clustering
48work that makes up the second phase of the project.
49
50The second phase of the project is now upon us. The DragonFly project's
51ultimate goal is to provide native clustering support in the kernel.
52This involves the creation of a sophisticated cache management
53framework for filesystem namespaces, file spaces, and VM spaces, which
54allows heavily interactive programs to run across multiple machines with
55cache coherency fully guaranteed in all respects. This also involves being
56able to chop up resources, including the cpu by way of a controlled VM
57context, for safe assignment to unsecured third-party clusters over the
58internet (though the security of such clusters itself might be in doubt,
59the first and most important thing is for systems donating resources to not
60be made vulnerable through their donation).
b043b812 61
b043b812 62
bef9be4c 63
473fa66e 64