[BACK]Return to upgrade.html CVS log [TXT] [DIR] Up to [LON-CAPA] / doc / build

Diff for /doc/build/Attic/upgrade.html between versions 1.7 and 1.10

version 1.7, 2002/04/23 11:55:11 version 1.10, 2002/04/23 13:01:14
Line 6 Line 6
 </head>  </head>
 <body>  <body>
 <!-- preamble start -->  <!-- preamble start -->
 <h1>LON-CAPA Upgrade</h1>  <p>
 <h3>Current Upgrade Procedure</h3>  There are three steps for upgrading the software on your LON-CAPA server.
   </p>
   <ul>
   <li><a href="#upgrade">
   Upgrading LON-CAPA files</a></li>
   <li><a href="#checkrpms">
   Checking your Linux RPMs</a></li>
   <li><a href="#testing">
   Testing to see if the LON-CAPA server is operational</a></li>
   </ul>
   <br />&nbsp;<br />
 <!-- preamble end -->  <!-- preamble end -->
 <!-- maintext start -->  <!-- maintext start -->
   <a name="upgrade" />
   <h3>Upgrading LON-CAPA files</h3>
 <p>  <p>
 Scott Harrison  Download the most current
   <a href="http://install.lon-capa.org/versions/current/loncapa.tar.gz">
   loncapa.tar.gz</a>.
 </p>  </p>
 <p>  <p>
 Last updated: 4/18/2001  The <strong>UPDATE</strong> command will refresh your filesystem with all
   the latest LON-CAPA software.
 </p>  </p>
   <table bgcolor="#aaaaaa" border="1">
   <tr><td><tt>./UPDATE</tt></td></tr>
   </table>
   <a name="checkrpms" />
   <h3>Checking your Linux RPMs</h3>
 <p>  <p>
 LON-CAPA system releases currently are not released under version  The <strong>CHECKRPMS</strong> command will check the RPMs on your machine
 numbers given the fast pace of system development.  To upgrade your  against an FTP repository.
 system, you need to   
 <ol>  
 <li>Make sure your software packages are up-to-date  
 (based on install.lon-capa.org).</li>  
 <ul>  
 <li>As root, run the script <tt>/usr/sbin/loncapaverifypackages</tt>.    
 If packages are out-of-date, this script will output  
 the out-of-date packages.  Packages that this script identifies as  
 "should not be here", are packages that you may wish to remove to  
 improve system security.  (These packages may represent important  
 modifications of your institution, so do with care.  Removing  
 packages is done with the command: <tt>rpm -e --nodeps PACKAGE_NAME</tt>.</li>  
 </ul>  
 <li>Upgrade old software packages.</li>  
 <ul>  
 <li>Upgrade software packages by either</li>  
 <ul>  
 <li>Running <tt>/usr/sbin/loncapaupgradepackages</tt>.</li>  
 <li>Or, going to <a href="http://install.lon-capa.org/3.1/SupplementalRPMS/">http://install.lon-capa.org/3.1/SupplementalRPMS/</a>,  
 you can individually download each package from the world-wide web.  You   
 then need to enter the command:  
 <tt>rpm -Uvh --force PACKAGE_RPM_FILE_NAME</tt> to upgrade your system  
 for each package.</li>  
 </ul>  
 </ul>  
 <li>Make the LON-CAPA base files up to date (based on  
 install.lon-capa.org).</li>  
 <ul>  
 <li><B>[optional]</B> Run the script  
 <tt>/usr/sbin/loncapaverifybasepackage</tt>.  Then view  
 /home/httpd/html/dev/index.html for the verification report.  
 If there are no real changes, then you do not need to make your files  
 up-to-date.</li>  
 <li>Download the most recent LON-CAPA rpm (<a href="http://install.lon-capa.org/3.1/loncapafiles/LON-CAPA-base-3.1-1.i386.rpm">  
 LON-CAPA-base-3.1-1.i386.rpm</a>).  <tt>rpm -Uvh --force LON-CAPA-base-3.1-1.i386.rpm</tt> will upgrade your software package files.</li>  
 </ul>  
 <li>Restore configuration files.</li>  
 <ul>  
 <li>As you run /usr/sbin/loncapaupgradepackages or enter in  
 <tt>rpm -Uvh --force</tt> commands, you may  
 see messages appear on your screen such as:  
 <br /><tt>warning: /etc/httpd/conf/access.conf saved as  
 /etc/httpd/conf/access.conf.rpmsave</tt>  
 <br />You can probably just type in commands like:  
 <br /><tt>cp /etc/httpd/conf/access.conf.rpmsave  
 /etc/httpd/conf/access.conf</tt>  
 <br />to restore your configurations.  However, it is worthwhile to use the  
 'diff' command to make sure that you are not accidentally losing important  
 updates to the configuration files.    
 <li>Alternatively, you can run <tt>/usr/sbin/loncaparestoreconfigurations</tt>  
 to "smartly" run through the system and restore LON-CAPA configuration  
 values.</li>  
 </ul>  
 <li>Restart the LON-CAPA networking processes  
 <ul>  
 <li><tt>/etc/rc.d/init.d/loncontrol restart</tt></li>  
 </ul>  
 <li>Should you wish to automate the updating of your LON-CAPA base files, you can (at your own risk) run a script which will  
 do all of this automatically.  You can run this script by entering the command:  
 <TT>/usr/sbin/loncapaautoupgrade</TT></li>  
 </ol>  
 </p>  </p>
 <h3>Future Upgrade Procedure (not yet implemented)</h3>  <table bgcolor="#aaaaaa" border="1">
   <tr><td><tt>./CHECKRPMS</tt></td></tr>
   </table>
   <a name="testing" />
   <h3>Testing to see if the LON-CAPA server is operational</h3>
 <p>  <p>
 In the future, LON-CAPA will be a versioned system that is released via CD.  The <strong>TEST</strong> command will check the installation software,
 The upgrade procedure will be to insert the CD and follow instructions.  The CD  the perl libraries on your system, the MySQL database, and
 upgrade procedure is already defined and somewhat implemented, but awaits  will also automatically test the real-time operation of the 
 completion.  LON-CAPA Apache web server.
 </p>  </p>
   <table bgcolor="#aaaaaa" border="1">
   <tr><td><tt>./TEST</tt></td></tr>
   </table>
 <!-- maintext end -->  <!-- maintext end -->
 </body>  </body>
 </html>  </html>
Removed from v.1.7  
changed lines
  Added in v.1.10

FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>