Миф о назначении DragonFly BSD: одна ОС на нескольких физических машинах?
#/bin/sh
somedir=somedir
list="`echo "$somedir"/*`"
test "$list" = "$somedir/*" && echo "$somedir is empty"
# dot prefixed entries would be skipped though, you have to explicitly check them
Эту информацию легко найти в Google -.
Да, DragonFly BSD намеревается поддерживать «кластеризацию образов одной системы» в какой-то момент, как указано на веб-странице истории проекта .
DragonFly BSD has been going through rapid and ever increasing development since the fork. One of the important works 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 to 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 regard to the third party applications and base system utilities needed to make any system usable in production. This resulted in the adoption of the pkgsrc framework for management of all non-base-system third-party applications in order to pool our resources with other BSD projects using this framework.
In the 2007-2008 time frame, a new filesystem called HAMMER was developed for DragonFly BSD. HAMMER saw its first light of day in July 2008 with the DragonFly 2.0 release. This filesystem has been designed to solve numerous issues and to add many new capabilities to DragonFly, such as fine-grained history retention (snapshots), instant crash recovery, and near real-time mirroring. The HAMMER filesystem is also intended to serve as a basis for the clustering and other work that makes up the second phase of the project.
Обратите внимание, что в самой последней версии операционной системы(версии 5.0)HAMMER2 не поддерживает кластеризацию.
Также читайте (несколько старую )статью InformIT:DragonFly BSD :UNIX для кластеров? .