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