Add some information about DragenFly.

PR:			docs/70310
Submitted by:		Joel Dahl <joel at automatvapen dot se>
Approved by:		maintainer timeout
This commit is contained in:
Remko Lodder 2005-04-17 11:59:28 +00:00
parent 0528b716aa
commit d0a1f12465
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=24308

View file

@ -172,9 +172,11 @@
and the first version of FreeBSD was not ready until the end of the and the first version of FreeBSD was not ready until the end of the
year. In the meantime, the code base had diverged sufficiently to year. In the meantime, the code base had diverged sufficiently to
make it difficult to merge. In addition, the projects had different make it difficult to merge. In addition, the projects had different
aims, as we will see below. In 1996, a further project, aims, as we will see below. In 1996,
<ulink url="http://www.OpenBSD.org/">OpenBSD</ulink>, split off from <ulink url="http://www.OpenBSD.org/">OpenBSD</ulink> split off from
NetBSD.</para> NetBSD, and in 2003,
<ulink url="http://www.dragonflybsd.org/">DragonFlyBSD</ulink> split
of from FreeBSD.</para>
</sect1> </sect1>
<sect1> <sect1>
@ -240,7 +242,8 @@
distributions, of course). In the following section, we will look at BSD distributions, of course). In the following section, we will look at BSD
and compare it to Linux. The description applies most closely to and compare it to Linux. The description applies most closely to
FreeBSD, which accounts for an estimated 80% of the BSD installations, FreeBSD, which accounts for an estimated 80% of the BSD installations,
but the differences from NetBSD and OpenBSD are small.</para> but the differences from NetBSD, OpenBSD and DragonFlyBSD are small.
</para>
<sect2> <sect2>
<title>Who owns BSD?</title> <title>Who owns BSD?</title>
@ -348,7 +351,7 @@
<sect2> <sect2>
<title>BSD releases</title> <title>BSD releases</title>
<para>Each BSD project provides the system in three different <para>FreeBSD, NetBSD and OpenBSD provides the system in three different
<quote>releases</quote>. As with Linux, releases are assigned a <quote>releases</quote>. As with Linux, releases are assigned a
number such as 1.4.1 or 3.5. In addition, the version number has a number such as 1.4.1 or 3.5. In addition, the version number has a
suffix indicating its purpose:</para> suffix indicating its purpose:</para>
@ -402,7 +405,7 @@
<title>What versions of BSD are available?</title> <title>What versions of BSD are available?</title>
<para>In contrast to the numerous Linux distributions, there are only <para>In contrast to the numerous Linux distributions, there are only
three open source BSDs. Each BSD project maintains its own source four major open source BSDs. Each BSD project maintains its own source
tree and its own kernel. In practice, though, there appear to be tree and its own kernel. In practice, though, there appear to be
fewer divergences between the userland code of the projects than there fewer divergences between the userland code of the projects than there
is in Linux.</para> is in Linux.</para>
@ -437,6 +440,14 @@
exchanges and US Government departments. Like NetBSD, it runs on exchanges and US Government departments. Like NetBSD, it runs on
a number of platforms.</para> a number of platforms.</para>
</listitem> </listitem>
<listitem>
<para>DragonFlyBSD aims for high performance and scalability under
everything from a single-node UP system to a massively clustered system.
DragonFlyBSD has several long-range technical goals, but focus lies on
providing a SMP-capable infrastructure that is easy to understand,
maintain and develop for.</para>
</listitem>
</itemizedlist> </itemizedlist>
<para>There are also two additional BSD &unix; operating systems which are not <para>There are also two additional BSD &unix; operating systems which are not