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

Annotation of doc/build/upgrade.html, revision 1.7

1.6       harris41    1: <html>
                      2: <head>
                      3: <title>LON-CAPA Upgrade</title>
1.7     ! harris41    4: <!-- pdfahref upgrade.pdf -->
        !             5: <!-- button UPGRADE -->
1.6       harris41    6: </head>
                      7: <body>
1.7     ! harris41    8: <!-- preamble start -->
1.6       harris41    9: <h1>LON-CAPA Upgrade</h1>
                     10: <h3>Current Upgrade Procedure</h3>
1.7     ! harris41   11: <!-- preamble end -->
        !            12: <!-- maintext start -->
1.6       harris41   13: <p>
1.5       harris41   14: Scott Harrison
1.6       harris41   15: </p>
                     16: <p>
                     17: Last updated: 4/18/2001
                     18: </p>
                     19: <p>
1.1       harris41   20: LON-CAPA system releases currently are not released under version
                     21: numbers given the fast pace of system development.  To upgrade your
                     22: system, you need to 
1.6       harris41   23: <ol>
                     24: <li>Make sure your software packages are up-to-date
                     25: (based on install.lon-capa.org).</li>
                     26: <ul>
                     27: <li>As root, run the script <tt>/usr/sbin/loncapaverifypackages</tt>.  
1.3       harris41   28: If packages are out-of-date, this script will output
1.6       harris41   29: the out-of-date packages.  Packages that this script identifies as
                     30: "should not be here", are packages that you may wish to remove to
                     31: improve system security.  (These packages may represent important
                     32: modifications of your institution, so do with care.  Removing
                     33: packages is done with the command: <tt>rpm -e --nodeps PACKAGE_NAME</tt>.</li>
                     34: </ul>
                     35: <li>Upgrade old software packages.</li>
                     36: <ul>
                     37: <li>Upgrade software packages by either</li>
                     38: <ul>
                     39: <li>Running <tt>/usr/sbin/loncapaupgradepackages</tt>.</li>
                     40: <li>Or, going to <a href="http://install.lon-capa.org/3.1/SupplementalRPMS/">http://install.lon-capa.org/3.1/SupplementalRPMS/</a>,
                     41: you can individually download each package from the world-wide web.  You 
                     42: then need to enter the command:
                     43: <tt>rpm -Uvh --force PACKAGE_RPM_FILE_NAME</tt> to upgrade your system
                     44: for each package.</li>
                     45: </ul>
                     46: </ul>
                     47: <li>Make the LON-CAPA base files up to date (based on
                     48: install.lon-capa.org).</li>
                     49: <ul>
                     50: <li><B>[optional]</B> Run the script
                     51: <tt>/usr/sbin/loncapaverifybasepackage</tt>.  Then view
                     52: /home/httpd/html/dev/index.html for the verification report.
                     53: If there are no real changes, then you do not need to make your files
                     54: up-to-date.</li>
                     55: <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">
                     56: 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>
                     57: </ul>
                     58: <li>Restore configuration files.</li>
                     59: <ul>
                     60: <li>As you run /usr/sbin/loncapaupgradepackages or enter in
                     61: <tt>rpm -Uvh --force</tt> commands, you may
1.1       harris41   62: see messages appear on your screen such as:
1.6       harris41   63: <br /><tt>warning: /etc/httpd/conf/access.conf saved as
                     64: /etc/httpd/conf/access.conf.rpmsave</tt>
                     65: <br />You can probably just type in commands like:
                     66: <br /><tt>cp /etc/httpd/conf/access.conf.rpmsave
                     67: /etc/httpd/conf/access.conf</tt>
                     68: <br />to restore your configurations.  However, it is worthwhile to use the
                     69: 'diff' command to make sure that you are not accidentally losing important
                     70: updates to the configuration files.  
                     71: <li>Alternatively, you can run <tt>/usr/sbin/loncaparestoreconfigurations</tt>
                     72: to "smartly" run through the system and restore LON-CAPA configuration
                     73: values.</li>
                     74: </ul>
                     75: <li>Restart the LON-CAPA networking processes
                     76: <ul>
                     77: <li><tt>/etc/rc.d/init.d/loncontrol restart</tt></li>
                     78: </ul>
                     79: <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
1.3       harris41   80: do all of this automatically.  You can run this script by entering the command:
1.6       harris41   81: <TT>/usr/sbin/loncapaautoupgrade</TT></li>
                     82: </ol>
                     83: </p>
                     84: <h3>Future Upgrade Procedure (not yet implemented)</h3>
                     85: <p>
1.1       harris41   86: In the future, LON-CAPA will be a versioned system that is released via CD.
                     87: The upgrade procedure will be to insert the CD and follow instructions.  The CD
                     88: upgrade procedure is already defined and somewhat implemented, but awaits
                     89: completion.
1.6       harris41   90: </p>
1.7     ! harris41   91: <!-- maintext end -->
1.6       harris41   92: </body>
                     93: </html>
FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>