cvs commit: www/en/advocacy myths.sgml

Sun Jan 8 12:12:50 PST 2006

On Sun, Jan 08, 2006 at 06:37:47PM +0000, Pav Lucistnik wrote:
> pav         2006-01-08 18:37:47 UTC
> 
>   FreeBSD doc repository
> 
>   Modified files:
>     en/advocacy          myths.sgml 
>   Log:
>   - Add more derivates
>   - Fix typo (missing dot)
>   

===================================================================
RCS file: /usr/local/www/cvsroot/FreeBSD/www/en/advocacy/myths.sgml,v
retrieving revision 1.29
retrieving revision 1.30
diff -u -p -r1.29 -r1.30

--- www/en/advocacy/myths.sgml	2005/12/30 13:38:53	1.29
+++ www/en/advocacy/myths.sgml	2006/01/08 18:37:47	1.30
@@ -1,6 +1,6 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" [
 <!ENTITY base CDATA "..">
-<!ENTITY date "$FreeBSD: /usr/local/www/cvsroot/FreeBSD/www/en/advocacy/myths.sgml,v 1.29 2005/12/30 13:38:53 ceri Exp $">
+<!ENTITY date "$FreeBSD: /usr/local/www/cvsroot/FreeBSD/www/en/advocacy/myths.sgml,v 1.30 2006/01/08 18:37:47 pav Exp $">
 <!ENTITY title "FreeBSD Advocacy Project">
 <!ENTITY % navincludes SYSTEM "../includes.navabout.sgml"> %navincludes;
 <!ENTITY % includes SYSTEM "../includes.sgml"> %includes;
@@ -136,23 +136,79 @@
       or derivative works of *BSD</h3>
 
     <p>You can. You just need to say in the documentation and source
-      files where the code is derived from.</p>
+      files where the code is derived from. A bunch of derivative
+      projects exists:</p>
 
-    <p>For example, PicoBSD is a tailored distribution of FreeBSD that
-      fits on a floppy. It's great for turning a diskless 386 PC into a
-      router or a network print server. Another popular FreeBSD derivate
-      is FreeSBIE, a complete desktop running off the CD-ROM.</p>
-
-    <p>The Whistle Interjet is a ``network appliance'' that acts as a
-      router, web server, mailhost (and other functionality), and can be
-      configured using a web browser. The underlying operating system is
-      FreeBSD, and Whistle have contributed many of their code
-      enhancements back to the FreeBSD project (while keeping enough of
-      them proprietary that they can stay in business).</p>
-
-    <p>The OpenBSD project started as a spinoff from the NetBSD project, and
-      has since evolved its own distinctive approach. Similarly, DragonflyBSD
-      derives from FreeBSD 4.X.</p>
+    <ul>
+	<li><p><a href="http://www.dragonflybsd.org/">
+	  DragonflyBSD</a> started as a code fork from

(For style consistency) we should not wrap like this the content of
<a></a> tags.

+	  FreeBSD 4.X, but it has since its own user community and
+	  development goals.</p></li>
+
+	<li><p><a href="http://www.trustedbsd.org/">
+	   TrustedBSD</a> provides a set of trusted operating system
+	   extensions to the FreeBSD operating system, targeting the
+	   Common Criteria for Information Technology Security
+	   Evaluation (CC).  This project is still under development,
+	   and much of the code is destined to make its way back into
+	   the base FreeBSD operating system, but the development
+	   takes place separately.<p></li>
+
+	<li><p><a href="http://www.freesbie.org/">
+	  FreeSBIE</a> is a complete desktop running off the CD-ROM.
+	  It can also be installed, but extremely useful for diskless
+	  computers.</p></li>
+
+	<li><p><a href="http://frenzy.org.ua/eng/">
+	  Frenzy</a> is another live-CD distribution, but customized
+	  for administering tasks.  It contains software for hardware
+	  tests, file system checks, security checks, network setup
+	  and analysis.<p></li>
+
+	<li><p><a href="http://people.freebsd.org/~picobsd/picobsd.html">
+	  PicoBSD</a> is a tailored distribution of FreeBSD that fits
+	  on a floppy.  It is great for turning diskless 386 PC into a
+	  router or a network print server.  It is based on FreeBSD
+	  3.x.</p></li>
+

The old text regarding PicoBSD was correct, this new one is not.
PicoBSD is not based on FreeBSD 3.X but on the source of the system used
to build it (/usr/src/release/picobsd).  The provided link is outdated
(and will never be updated), a better solution would be to point on
/usr/src/release/picobsd or nothing.

+	<li><p><a href="../projects/nanobsd/">
+	  NanoBSD</a> is another project to produce a reduced versions
+	  of FreeBSD to put it on a Compact Flash card or other mass
+	  storage.</p></li>
+

It would be interesting to mention that NanoBSD is supported by the
FreeBSD Project and is part of the base tree.

+	<li><p><a href="http://www.tinybsd.org/tinybsd">
+	  TinyBSD</a> is a set of tools made up of shell scripts
+	  designed to allow easy development of Embedded Systems based
+	  on FreeBSD 5.x and 6.x.</p></li>
+
[...]

s/.x/.X/ for consistency.

Marc
