View | Details | Raw Unified | Return to bug 70310
Collapse All | Expand All

(-)new.article.sgml (-6 / +17 lines)
Lines 170-178 Link Here
170
      and the first version of FreeBSD was not ready until the end of the
170
      and the first version of FreeBSD was not ready until the end of the
171
      year.  In the meantime, the code base had diverged sufficiently to
171
      year.  In the meantime, the code base had diverged sufficiently to
172
      make it difficult to merge.  In addition, the projects had different
172
      make it difficult to merge.  In addition, the projects had different
173
      aims, as we will see below.  In 1996, a further project,
173
      aims, as we will see below.  In 1996,
174
      <ulink url="http://www.OpenBSD.org/">OpenBSD</ulink>, split off from
174
      <ulink url="http://www.OpenBSD.org/">OpenBSD</ulink> split off from
175
      NetBSD.</para>
175
      NetBSD, and in 2003,
176
      <ulink url="http://www.dragonflybsd.org/">DragonFlyBSD</ulink> split
177
      of from FreeBSD.</para>
176
  </sect1>
178
  </sect1>
177
  
179
  
178
  <sect1>
180
  <sect1>
Lines 238-244 Link Here
238
      distributions, of course).  In the following section, we will look at BSD
240
      distributions, of course).  In the following section, we will look at BSD
239
      and compare it to Linux.  The description applies most closely to
241
      and compare it to Linux.  The description applies most closely to
240
      FreeBSD, which accounts for an estimated 80% of the BSD installations,
242
      FreeBSD, which accounts for an estimated 80% of the BSD installations,
241
      but the differences from NetBSD and OpenBSD are small.</para>
243
      but the differences from NetBSD, OpenBSD and DragonFlyBSD are small.
244
      </para>
242
245
243
    <sect2>
246
    <sect2>
244
      <title>Who owns BSD?</title>
247
      <title>Who owns BSD?</title>
Lines 345-351 Link Here
345
    <sect2>
348
    <sect2>
346
      <title>BSD releases</title>
349
      <title>BSD releases</title>
347
350
348
      <para>Each BSD project provides the system in three different
351
      <para>FreeBSD, NetBSD and OpenBSD provides the system in three different
349
	<quote>releases</quote>.  As with Linux, releases are assigned a
352
	<quote>releases</quote>.  As with Linux, releases are assigned a
350
	number such as 1.4.1 or 3.5.  In addition, the version number has a
353
	number such as 1.4.1 or 3.5.  In addition, the version number has a
351
	suffix indicating its purpose:</para>
354
	suffix indicating its purpose:</para>
Lines 399-405 Link Here
399
      <title>What versions of BSD are available?</title>
402
      <title>What versions of BSD are available?</title>
400
403
401
      <para>In contrast to the numerous Linux distributions, there are only
404
      <para>In contrast to the numerous Linux distributions, there are only
402
	three open source BSDs.  Each BSD project maintains its own source
405
        four major open source BSDs.  Each BSD project maintains its own source
403
	tree and its own kernel.  In practice, though, there appear to be
406
	tree and its own kernel.  In practice, though, there appear to be
404
	fewer divergences between the userland code of the projects than there
407
	fewer divergences between the userland code of the projects than there
405
	is in Linux.</para>
408
	is in Linux.</para>
Lines 430-435 Link Here
430
	    choice of security-conscious organizations such as banks, stock
433
	    choice of security-conscious organizations such as banks, stock
431
	    exchanges and US Government departments.  Like NetBSD, it runs on
434
	    exchanges and US Government departments.  Like NetBSD, it runs on
432
	    a number of platforms.</para>
435
	    a number of platforms.</para>
436
	</listitem>
437
438
	<listitem>
439
	  <para>DragonFlyBSD aims for high performance and scalability under
440
	  everything from a single-node UP system to a massively clustered system.
441
	  DragonFlyBSD has several long-range technical goals, but focus lies on
442
	  providing a SMP-capable infrastructure that is easy to understand,
443
	  maintain and develop for.</para>
433
	</listitem>
444
	</listitem>
434
      </itemizedlist>
445
      </itemizedlist>
435
446

Return to bug 70310