Index: openacs-4/packages/acs-core-docs/www/xml/developers-guide/cvs.xml
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/developers-guide/cvs.xml,v
diff -u -N -r1.4.2.4 -r1.4.2.5
--- openacs-4/packages/acs-core-docs/www/xml/developers-guide/cvs.xml	16 Dec 2003 11:15:53 -0000	1.4.2.4
+++ openacs-4/packages/acs-core-docs/www/xml/developers-guide/cvs.xml	20 Feb 2004 22:06:11 -0000	1.4.2.5
@@ -54,7 +54,7 @@
             release tag.  These tags will be useful in upgrading and
             branching.  -m sets the version comment.</para>
             <screen>[root root]# <userinput>su - <replaceable>service0</replaceable></userinput>
-[service0 service0]$ <userinput>cd /web/<replaceable>service0</replaceable></userinput>
+[service0 service0]$ <userinput>cd /var/lib/aolserver/<replaceable>service0</replaceable></userinput>
 [service0 service0]$ <userinput>cvs import -m "initial install" <replaceable>service0</replaceable> OpenACS &cvsversiontag;</userinput>
 N <replaceable>service0</replaceable>/license.txt
 N <replaceable>service0</replaceable>/readme.txt
@@ -65,7 +65,7 @@
 
 [service0 service0]$
 <action>su - <replaceable>service0</replaceable>
-cd /web/<replaceable>service0</replaceable>
+cd /var/lib/aolserver/<replaceable>service0</replaceable>
 cvs import -m "initial install" <replaceable>service0</replaceable> OpenACS &cvsversiontag;</action></screen>
             <para>Move the original directory to a temporary location, and check out the cvs repository in its place.  If the service starts correctly, come back and remove the temporary copy of the uploaded files.</para>
             <screen>[service0 service0]$ <userinput>cd ..</userinput>
Index: openacs-4/packages/acs-core-docs/www/xml/kernel/bootstrap-acs.xml
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/kernel/bootstrap-acs.xml,v
diff -u -N -r1.4.2.1 -r1.4.2.2
--- openacs-4/packages/acs-core-docs/www/xml/kernel/bootstrap-acs.xml	19 Nov 2003 14:35:16 -0000	1.4.2.1
+++ openacs-4/packages/acs-core-docs/www/xml/kernel/bootstrap-acs.xml	20 Feb 2004 22:06:12 -0000	1.4.2.2
@@ -27,7 +27,7 @@
 Before OpenACS 3.3, the OpenACS startup process was extremely simple: after AOLserver
 performed its internal initialization (reading the configuration file,
 loading shared libraries and module code, etc.) it scanned through the Tcl
-library directory (generally <computeroutput>/web/</computeroutput><emphasis><computeroutput>yourservername</computeroutput></emphasis><computeroutput>/tcl</computeroutput>),
+library directory (generally <computeroutput>/var/lib/aolserver/</computeroutput><emphasis><computeroutput>yourservername</computeroutput></emphasis><computeroutput>/tcl</computeroutput>),
 sourcing each file in sequence. 
 </para>
 
@@ -69,9 +69,9 @@
 <para>Next AOLserver sources, in lexicographical order, each file in the
 <computeroutput>/tcl</computeroutput> directory. The first such file is
 <computeroutput>0-acs-init.tcl</computeroutput>, which doesn&#39;t do much directly except to
-determine the OpenACS path root (e.g., <computeroutput>/web/</computeroutput><emphasis><computeroutput>yourservername</computeroutput></emphasis>)
+determine the OpenACS path root (e.g., <computeroutput>/var/lib/aolserver/</computeroutput><emphasis><computeroutput>yourservername</computeroutput></emphasis>)
 by trimming the final component from the path to the Tcl library directory
-(<computeroutput>/web/</computeroutput><emphasis><computeroutput>yourservername</computeroutput></emphasis><computeroutput>/tcl</computeroutput>). But
+(<computeroutput>/var/lib/aolserver/</computeroutput><emphasis><computeroutput>yourservername</computeroutput></emphasis><computeroutput>/tcl</computeroutput>). But
 <computeroutput>0-acs-init.tcl</computeroutput>&#39;s has an important function, namely sourcing
 <computeroutput>/packages/acs-core/bootstrap.tcl</computeroutput>, which does the following:</para>
 
Index: openacs-4/packages/acs-core-docs/www/xml/kernel/rp-design.xml
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/kernel/rp-design.xml,v
diff -u -N -r1.5.2.3 -r1.5.2.4
--- openacs-4/packages/acs-core-docs/www/xml/kernel/rp-design.xml	15 Dec 2003 22:04:07 -0000	1.5.2.3
+++ openacs-4/packages/acs-core-docs/www/xml/kernel/rp-design.xml	20 Feb 2004 22:06:12 -0000	1.5.2.4
@@ -76,21 +76,21 @@
 
 <listitem>
 <para><emphasis role="strong">global pageroot</emphasis>
-(<emphasis role="strong">/web/<emphasis>servicename</emphasis>/www</emphasis>) -- Files appearing under
+(<emphasis role="strong">/var/lib/aolserver/<emphasis>servicename</emphasis>/www</emphasis>) -- Files appearing under
 this pageroot will be served directly off the base url
 http://www.<emphasis>servicename</emphasis>.com/</para>
 </listitem>
 
 <listitem>
 <para><emphasis role="strong">package root</emphasis>
-(<emphasis role="strong">/web/<emphasis>servicename</emphasis>/packages</emphasis>) -- Each subdirectory of
+(<emphasis role="strong">/var/lib/aolserver/<emphasis>servicename</emphasis>/packages</emphasis>) -- Each subdirectory of
 the package root is a package. A typical OpenACS installation will have several
 packages.</para>
 </listitem>
 
 <listitem>
 <para><emphasis role="strong">package pageroot</emphasis>
-(<emphasis role="strong">/web/<emphasis>servicename</emphasis>/packages/<emphasis>package_key</emphasis>/www</emphasis>)
+(<emphasis role="strong">/var/lib/aolserver/<emphasis>servicename</emphasis>/packages/<emphasis>package_key</emphasis>/www</emphasis>)
 -- This is the pageroot for the <emphasis>package_key</emphasis> package.</para>
 </listitem>