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