Index: openacs-4/packages/acs-core-docs/www/bootstrap-acs.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/bootstrap-acs.adp,v
diff -u -N -r1.4 -r1.4.2.1
--- openacs-4/packages/acs-core-docs/www/bootstrap-acs.adp	25 Apr 2018 08:38:27 -0000	1.4
+++ openacs-4/packages/acs-core-docs/www/bootstrap-acs.adp	2 Mar 2019 19:30:04 -0000	1.4.2.1
@@ -1,5 +1,5 @@
 
-<property name="context">{/doc/acs-core-docs {ACS Core Documentation}} {Bootstrapping OpenACS}</property>
+<property name="context">{/doc/acs-core-docs/ {ACS Core Documentation}} {Bootstrapping OpenACS}</property>
 <property name="doc(title)">Bootstrapping OpenACS</property>
 <master>
 <include src="/packages/acs-core-docs/lib/navheader"
@@ -9,9 +9,12 @@
 			rightLink="ext-auth-requirements" rightLabel="Next">
 		    <div class="sect1">
 <div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="bootstrap-acs" id="bootstrap-acs"></a>Bootstrapping OpenACS</h2></div></div></div><span style="color: red">&lt;authorblurb&gt;</span><p><span style="color: red">By <a class="ulink" href="mailto:jsalz\@mit.edu" target="_top">Jon Salz</a>
-</span></p><span style="color: red">&lt;/authorblurb&gt;</span><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc;"><li class="listitem"><p>Tcl code: /tcl/0-acs-init.tcl and
-/packages/acs-kernel/bootstrap.tcl</p></li></ul></div><p>This document describes the startup (bootstrapping) process for
+<a name="bootstrap-acs" id="bootstrap-acs"></a>Bootstrapping OpenACS</h2></div></div></div><div class="authorblurb">
+<p>By <a class="ulink" href="mailto:jsalz\@mit.edu" target="_top">Jon Salz</a>
+</p>
+OpenACS docs are written by the named authors, and may be edited by
+OpenACS documentation staff.</div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc;"><li class="listitem"><p>Tcl code: /tcl/0-acs-init.tcl and
+/packages/acs-bootstrap-installer/bootstrap.tcl</p></li></ul></div><p>This document describes the startup (bootstrapping) process for
 an AOLserver running OpenACS.</p><div class="sect2">
 <div class="titlepage"><div><div><h3 class="title">
 <a name="bootstrap-acs-bigpicture" id="bootstrap-acs-bigpicture"></a>The Big Picture</h3></div></div></div><p>Before OpenACS 3.3, the OpenACS startup process was extremely
@@ -29,38 +32,30 @@
 AOLserver/OpenACS startup.</p>
 </div><div class="sect2">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="bootstrap-acs-startup-process" id="bootstrap-acs-startup-process"></a>The Startup Process</h3></div></div></div><p>As soon as the <code class="computeroutput">nsd</code> daemon is
-executed by the <code class="computeroutput">init</code> process
-(or otherwise), AOLserver reads its configuration file and
-<code class="computeroutput">chroot</code>s itself if necessary. It
-then loads shared libraries indicated in the <code class="computeroutput">.ini</code> file (e.g., the Oracle driver and
-<code class="computeroutput">nssock</code>), and sources Tcl module
-files (generally in <code class="computeroutput">/home/aol30/modules/tcl</code>). This step is, and
-has always been, the same for all AOLservers, regardless of whether
-they are running OpenACS.</p><p>Next AOLserver sources, in lexicographical order, each file in
+<a name="bootstrap-acs-startup-process" id="bootstrap-acs-startup-process"></a>The Startup Process</h3></div></div></div><p>When <code class="computeroutput">nsd</code> is started, it
+reads its configuration file and <code class="computeroutput">chroot</code>s itself if necessary. It then loads
+the configured modules (e.g., Database and network drivers, Tcl
+module files). This step is, and has always been, the same for all
+NaviServer/AOLservers, regardless of whether they are running
+OpenACS (see the NaviServer/AOLserver documentation for more
+details).</p><p>Next AOLserver sources, in lexicographical order, each file in
 the <code class="computeroutput">/tcl</code> directory. The first
 such file is <code class="computeroutput">0-acs-init.tcl</code>,
 which doesn&#39;t do much directly except to determine the OpenACS
 path root (e.g., <code class="computeroutput">/var/lib/aolserver/</code><span class="emphasis"><em><code class="computeroutput">yourservername</code></em></span>) by trimming the
 final component from the path to the Tcl library directory
 (<code class="computeroutput">/var/lib/aolserver/</code><span class="emphasis"><em><code class="computeroutput">yourservername</code></em></span><code class="computeroutput">/tcl</code>).
 But <code class="computeroutput">0-acs-init.tcl</code>'s has an
-important function, namely sourcing <code class="computeroutput">/packages/acs-core/bootstrap.tcl</code>, which
-does the following:</p><div class="orderedlist"><ol class="orderedlist" type="1">
+important function, namely sourcing <code class="computeroutput">/packages/acs-bootstrap-installer/bootstrap.tcl</code>,
+which does the following:</p><div class="orderedlist"><ol class="orderedlist" type="1">
 <li class="listitem"><p>
 <span class="strong"><strong>Initialize some NSVs used by the
 core</strong></span>. These NSVs are documented in <code class="computeroutput">/packages/acs-core/apm-procs.tcl</code> - no need
 to worry about them unless you&#39;re an OpenACS core hacker.</p></li><li class="listitem"><p>
-<span class="strong"><strong>Verify the deletion of obsolete
-OpenACS files</strong></span>. The <code class="computeroutput">/tcl</code> directory has evolved quite a bit over
-the months and years, and a few files have come and gone. The
-<code class="computeroutput">/www/doc/removed-files.txt</code> file
-contains a list of files which <span class="emphasis"><em>must be
-deleted</em></span> from the AOLserver installation, at the risk of
-causing weird conflicts, e.g., having several security filters
-registered. <code class="computeroutput">bootstrap.tcl</code> scans
-through this list, logging error messages to the log if any of
-these files exist.</p></li><li class="listitem"><p>
+<span class="strong"><strong>Verify that OpenACS is fully
+installed</strong></span>. If not (e.g. at the first installation)
+it prompts a form for providing essential information about the
+installation.</p></li><li class="listitem"><p>
 <span class="strong"><strong>Source <code class="computeroutput">*-procs.tcl</code> files in the OpenACS
 core</strong></span>. We source each file matching the <code class="computeroutput">*-procs.tcl</code> glob in the <code class="computeroutput">/packages/acs-kernel</code> directory, in
 lexicographical order. These procedure are needed to perform any of
@@ -100,8 +95,8 @@
 </ol></div><p>At this point, <code class="computeroutput">bootstrap.tcl</code>
 is done executing. AOLserver proceeds to source the remaining files
 in the <code class="computeroutput">/tcl</code> directory (i.e.,
-unpackaged libraries) and begins listening for connections.</p><p><span class="cvstag">($&zwnj;Id: bootstrap-acs.xml,v 1.7 2006/07/17
-05:38:38 torbenb Exp $)</span></p>
+unpackaged libraries) and begins listening for connections.</p><div class="cvstag">($&zwnj;Id: bootstrap-acs.xml,v 1.7 2006/07/17
+05:38:38 torbenb Exp $)</div>
 </div>
 </div>
 <include src="/packages/acs-core-docs/lib/navfooter"