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

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

1.1       harris41    1: <HTML>
                      2: <HEAD>
                      3: <TITLE>LON-CAPA Upgrade</TITLE>
                      4: </HEAD>
                      5: <BODY>
                      6: <H1>LON-CAPA Upgrade</H1>
1.3     ! harris41    7: <H3>Current Upgrade Procedure</H3>
1.1       harris41    8: <P>
                      9: LON-CAPA system releases currently are not released under version
                     10: numbers given the fast pace of system development.  To upgrade your
                     11: system, you need to 
                     12: <OL>
1.2       harris41   13: <LI>Make sure your software packages are up-to-date (based on install.lon-capa.org).
1.1       harris41   14: <UL>
1.3     ! harris41   15: <LI>As root, run the script <TT>/usr/sbin/loncapaverifypackages</TT>.  
        !            16: If packages are out-of-date, this script will output
1.1       harris41   17: the out-of-date packages.  Packages that this script identifies as "should not be here",
                     18: are packages that you may wish to remove to improve system security.  (These packages
                     19: may represent important modifications of your institution, so do with care.  Removing
                     20: packages is done with the command: <TT>rpm -e --nodeps PACKAGE_NAME</TT>.
                     21: </UL>
                     22: <LI>Upgrade old software packages.
                     23: <UL>
                     24: <LI>Upgrade software packages by either
                     25: <UL>
1.3     ! harris41   26: <LI>Running <TT>/usr/sbin/loncapaupgradepackages</TT>.
        !            27: <LI>Or, going to <A HREF="http://install.lon-capa.org/3.1/SupplementalRPMS/">http://install.lon-capa.org/3.1/SupplementalRPMS/</A>,
        !            28: you can individually download each package from the world-wide web.  You then need to enter the command:
        !            29: <TT>rpm -Uvh --force PACKAGE_RPM_FILE_NAME</TT> to upgrade your system for each package.
1.1       harris41   30: </UL>
                     31: </UL>
1.3     ! harris41   32: <LI>Make the LON-CAPA base files up to date (based on install.lon-capa.org).
        !            33: <UL>
        !            34: <LI><B>[optional]</B> Run the script <TT>/usr/sbin/loncapaverifybasepackage</TT>.  Then view /home/httpd/html/dev/index.html for the verification report.
        !            35: If there are no real changes, then you do not need to make your files up-to-date.
        !            36: <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">
        !            37: 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.
        !            38: </UL>
1.1       harris41   39: <LI>Restore configuration files.
                     40: <UL>
                     41: <LI>As you run /usr/sbin/loncapaupgradepackages or enter in <TT>rpm -Uvh --force</TT> commands, you may
                     42: see messages appear on your screen such as:
                     43: <BR><TT>warning: /etc/httpd/conf/access.conf saved as /etc/httpd/conf/access.conf.rpmsave</TT>
                     44: <BR>You can probably just type in commands like:
                     45: <BR><TT>cp /etc/httpd/conf/access.conf.rpmsave /etc/httpd/conf/access.conf</TT>
                     46: <BR>to restore your configurations.  However, it is worthwhile to use the 'diff' command
                     47: to make sure that you are not accidentally losing important updates to the configuration
                     48: files.  
1.3     ! harris41   49: <LI>Alternatively, you can run <TT>/usr/sbin/loncaparestoreconfigurations</TT> to "smartly" run through the system and restore LON-CAPA configuration values.
1.1       harris41   50: </UL>
1.3     ! harris41   51: <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
        !            52: do all of this automatically.  You can run this script by entering the command:
        !            53: <TT>/usr/sbin/loncapaautoupgrade</TT>
1.1       harris41   54: </OL>
                     55: </P>
                     56: <H3>Future Upgrade Procedure (not yet implemented)</H3>
                     57: <P>
                     58: In the future, LON-CAPA will be a versioned system that is released via CD.
                     59: The upgrade procedure will be to insert the CD and follow instructions.  The CD
                     60: upgrade procedure is already defined and somewhat implemented, but awaits
                     61: completion.
                     62: </P>
                     63: </BODY>
                     64: </HTML>
FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>