Add some text to the "BSD Vision" and "Architectural Guidelines"

sections of this chapter.

Obtained from:	PHK's post to developers@ on 20 Nov 2000.

en_US.ISO8859-1/books/developers-handbook/introduction/chapter.sgml

@@ -1,14 +1,25 @@
 <!--
      The FreeBSD Documentation Project
 
-     $FreeBSD: doc/en_US.ISO8859-1/books/developers-handbook/introduction/chapter.sgml,v 1.2 2001/07/22 20:08:33 asmodai Exp $
+     $FreeBSD: doc/en_US.ISO8859-1/books/developers-handbook/introduction/chapter.sgml,v 1.3 2001/08/13 06:38:59 jim Exp $
 -->
 
 <chapter id="introduction">
+  <chapterinfo>
+    <authorgroup>
+      <author>
+        <firstname>Murray</firstname>
+        <surname>Stokely</surname>
+        <contrib>This chapter was written by </contrib>
+      </author>
+      <author>
+        <firstname>Jeroen</firstname>
+        <surname>Ruigrok van der Werven</surname>
+      </author>
+    </authorgroup>
+  </chapterinfo>
   <title>Introduction</title>
 
-  <para>This chapter was written by &a.murray; and &a.asmodai;.</para>
-
   <sect1>
     <title>Developing on FreeBSD</title>
 
@@ -27,18 +38,59 @@
   </sect1>
 
   <sect1>
-    <title>* The BSD Vision</title>
+    <title>The BSD Vision</title>
 
-    <para></para>
+    <para>To produce the best UNIX-like operating system package
+      possible, with due respect to the original software tools
+      ideology as well as useability, performance and
+      stability.</para>
   </sect1>
  
   <sect1>
-    <title>* Architectural Overview</title>
+    <title>Architectural Guidelines</title>
-    <para></para>
+
+    <para>Our idealogy can be described by the following
+    guidelines</para>
+
+    <itemizedlist>
+
+      <listitem><para>Do not add new functionality unless an
+        implementor cannot complete a real application without
+        it.</para></listitem>
+
+      <listitem><para>It is as important to decide what a system is
+        not as to decide what it is. Do not serve all the world's
+        needs; rather, make the system extensible so that additional
+        needs can be met in an upwardly compatible
+        fashion.</para></listitem>
+
+      <listitem><para>The only thing worse than generalizing from one
+        example is generalizing from no examples at
+        all. </para></listitem>
+
+      <listitem><para>If a problem is not completely understood, it is
+        probably best to provide no solution at all.</para></listitem>
+
+      <listitem><para>If you can get 90 percent of the desired effect
+        for 10 percent of the work, use the simpler
+        solution.</para></listitem>
+
+      <listitem><para>Isolate complexity as much as
+        possible.</para></listitem>
+
+      <listitem><para>Provide mechanism, rather than policy. In
+        particular, place user interface policy in the client's
+        hands.</para></listitem>
+
+     </itemizedlist>
+
+     <para>From Scheifler & Gettys: "X Window System"</para>
+
   </sect1>
 
   <sect1>
-    <title>The Layout of <filename class="directory">/usr/src</filename></title>
+    <title>The Layout of 
+      <filename class="directory">/usr/src</filename></title>
 
     <para>The complete source code to FreeBSD is available from our
       public CVS repository.  The source code is normally installed in