From e730340254192ab339626fa29d108eacea5d69c4 Mon Sep 17 00:00:00 2001 From: JackUack Date: Tue, 24 May 2011 06:39:59 -0700 Subject: [PATCH] --- history/index.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/history/index.mdwn b/history/index.mdwn index e3eb9332..e7789062 100644 --- a/history/index.mdwn +++ b/history/index.mdwn @@ -1,5 +1,5 @@ A technical introduction: The ultimate goal of the DragonFly project at its inception was to provide native clustering support in the kernel. This type of functionality requires a sophisticated cache management framework for filesystem namespaces, file spaces and VM spaces. These and other features eventually culminate in the ability to allow heavily interactive programs to run across multiple machines with cache coherency fully guaranteed in all respects. This also requires being able to divide resources, including the cpu by way of a controlled VM context, for safe assignment to potentially unsecured third-party clusters over the internet. This original design direction, although no longer the primary goal of the DragonFly BSD project, has influenced many of the design decisions made in the intervening years. While full cache coherency is no longer a top level goal, filesystem coherency is, and that direction continues to guide the project in a number of ways. - +[weight loss](http://weightlosstips4u.org) DragonFly has been going through rapid and ever increasing development since the fork in 2003. This work has included the simplification and general cleanup of the majority of the kernel subsystems. This work was originally intended to support single system image clustering, but has had the effect of making the kernel much more reliable, understandable and easily maintainable. One of the fundamental synchronization concepts that DragonFly uses throughout the kernel, the token, lends itself directly to ease of maintenance and understandability of the kernel. During the first major phase of the project, which lasted until early 2007, the DragonFly project focused on rewriting most of the major kernel subsystems to implement required abstractions and support mechanics for the second phase of the project, which at the time was intended to be single system image clustering. This involved a great deal of work in nearly every subsystem, particularly the filesystem APIs and kernel core. During this time a paramount goal was to keep the system updated with regards to the third party applications and base system utilities needed to make any system usable in production. This resulted in the adoption the [pkgsrc](http://www.pkgsrc.org/) system for management of all non-base-system third-party applications in order to pool our resources with other BSD projects using the system. -- 2.41.0