Index: openacs-4/packages/acs-core-docs/www/upgrade-openacs-files.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/upgrade-openacs-files.html,v
diff -u -r1.9 -r1.10
--- openacs-4/packages/acs-core-docs/www/upgrade-openacs-files.html	18 Mar 2004 12:39:07 -0000	1.9
+++ openacs-4/packages/acs-core-docs/www/upgrade-openacs-files.html	22 Mar 2004 12:46:37 -0000	1.10
@@ -10,7 +10,7 @@
 cp -r openacs-4-6/* openacs-4
 exit</span></span></pre></li><li><p>
           <span class="strong">Upgrading files for a site in a private CVS repository</span>
-        </p><div class="figure"><a name="id2533680"></a><p class="title"><b>Figure�5.2.�Upgrading a local CVS repository</b></p><div class="mediaobject" align="center"><img src="images/upgrade-cvs.png" align="middle" alt="Upgrading a local CVS repository"></div></div><div class="itemizedlist"><ul type="circle"><li><p><b>Step 1: Import new CVS code.�</b>There are two common ways to get new OpenACS code into your local CVS repository - via tarball or with a working CVS checkout of OpenACS.  Both methods work well for starting your local repository; the second method is better for incremental additions or upgrades.</p><div class="itemizedlist"><ul type="disc"><li><p><b>(a): via tarball.�</b>Download a <a href="http://openacs.org/projects/openacs/download" target="_top">current tarball</a> and unpack the new files into a working directory.</p><pre class="screen">[root root]# <b class="userinput"><tt>su - <span class="replaceable"><span class="replaceable">service0</span></span></tt></b>
+        </p><div class="figure"><a name="id2533752"></a><p class="title"><b>Figure�5.2.�Upgrading a local CVS repository</b></p><div class="mediaobject" align="center"><img src="images/upgrade-cvs.png" align="middle" alt="Upgrading a local CVS repository"></div></div><div class="itemizedlist"><ul type="circle"><li><p><b>Step 1: Import new CVS code.�</b>There are two common ways to get new OpenACS code into your local CVS repository - via tarball or with a working CVS checkout of OpenACS.  Both methods work well for starting your local repository; the second method is better for incremental additions or upgrades.</p><div class="itemizedlist"><ul type="disc"><li><p><b>(a): via tarball.�</b>Download a <a href="http://openacs.org/projects/openacs/download" target="_top">current tarball</a> and unpack the new files into a working directory.</p><pre class="screen">[root root]# <b class="userinput"><tt>su - <span class="replaceable"><span class="replaceable">service0</span></span></tt></b>
 [service0 aolserver]$ <b class="userinput"><tt>cd /tmp</tt></b>
 [service0 tmp]$ <b class="userinput"><tt>tar xzf openacs-4-6.tgz</tt></b>
 [service0 tmp]$ <b class="userinput"><tt>cd openacs-4.6</tt></b></pre></li><li><p><b>(b): via cvs working checkout.�</b>Create a CVS checkout from OpenACS.  The first time you do this, you will need to create the checkout directory.  We use one dedicated directory for each branch of OpenACS - if you are using OpenACS 5.0,x, you only need an OpenACS 5.0 branch.  The <span class="replaceable"><span class="replaceable">openacs-5-0-compat</span></span> tag identifies the latest released version of OpenACS 5.0 (ie, 5.0.3 or 5.0.4) and the latest compatible version of each package, including .LRN.  Each minor release of OpenACS since 5.0 has this tagging structure.  (Ie., OpenACS 5.1.x has <tt class="computeroutput">openacs-5-1-compat</tt>.)</p><pre class="screen">[root root]# <b class="userinput"><tt>su - <span class="replaceable"><span class="replaceable">service0</span></span></tt></b>
@@ -37,7 +37,7 @@
       </p><div class="orderedlist"><ol type="1"><li><pre class="screen">[service0 ~]$ <b class="userinput"><tt>cd /var/lib/aolserver/<span class="replaceable"><span class="replaceable">service0</span></span></tt></b>
 [service0 service0]$ <b class="userinput"><tt>cvs up -Pd</tt></b>
 (CVS feedback)
-[service0 service0]$</pre></li></ol></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2534050"></a>Upgrading a Production Site Safely</h3></div></div><div></div></div><p>If you are upgrading a production OpenACS site which is on a private CVS tree, this process lets you do the upgrade without risking extended downtime or an unusable site:</p><div class="orderedlist"><ol type="1"><li><p>Declare a freeze on new cvs updates - ie, you cannot run cvs update
+[service0 service0]$</pre></li></ol></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2534122"></a>Upgrading a Production Site Safely</h3></div></div><div></div></div><p>If you are upgrading a production OpenACS site which is on a private CVS tree, this process lets you do the upgrade without risking extended downtime or an unusable site:</p><div class="orderedlist"><ol type="1"><li><p>Declare a freeze on new cvs updates - ie, you cannot run cvs update
    on the production site</p></li><li><p>
             Make a manual backup of the production site in addition to the
    automated backups</p></li><li><p>Import the new code (for example, OpenACS 5.0.4, openacs-5-0-compat versions of