[BACK]Return to upgrade.html CVS log [TXT] [DIR] Up to [LON-CAPA] / doc / build
File:  [LON-CAPA] / doc / build / Attic / upgrade.html
Revision 1.2: download - view: text, annotated - select for diffs
Thu Oct 26 07:31:16 2000 UTC (24 years ago) by harris41
Branches: MAIN
CVS tags: HEAD
beginning to modify

<HTML>
<HEAD>
<TITLE>LON-CAPA Upgrade</TITLE>
</HEAD>
<BODY>
<H1>LON-CAPA Upgrade</H1>
<H3>Current Upgrade Procedure (Almost)</H3>
<P>
LON-CAPA system releases currently are not released under version
numbers given the fast pace of system development.  To upgrade your
system, you need to 
<OL>
<LI>Make sure your software packages are up-to-date (based on install.lon-capa.org).
<UL>
<LI>As root, run the script <A HREF="http://install.lon-capa.org/verify/scripts/loncapaverifypackages">
loncapaverifypackages</A>.  This script should be present on your system in the file
/usr/sbin/loncapaverifypackages.  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>.
</UL>
<LI>Upgrade old software packages.
<UL>
<LI>Upgrade software packages by either
<UL>
<LI>Running /usr/sbin/<A HREF="http://www.lon-capa.org/install/verify/scripts/loncapaupgradepackages">loncapaupgradepackages</A>.
<LI>Or, going to <A HREF="http://www.lon-capa.org/install/RPMS/">http://www.lon-capa.org/install/RPMS/</A>,
you can individual 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.
</UL>
</UL>
<LI>Restore configuration files.
<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 /usr/sbin/<A HREF="http://www.lon-capa.org/install/verify/scripts/loncaparestoreconfigurations">loncaparestoreconfigurations</A> to "smartly" run through the system and restore LON-CAPA configuration values.
</UL>
<LI>Should you wish to automate all of this, you can (at your own risk) enable a script which will
do all of this automatically.  <B>This definitely should NOT be implemented on a system that students
are using)</B>.  You can enable this script by entering the command:
<TT>cp /usr/sbin/<A HREF="http://www.lon-capa.org/install/verify/scripts/loncapaautoupgrade">loncapaautoupgrade</A> /etc/cron.daily/loncapaautoupgrade</TT>
</OL>
</P>
<H3>Future Upgrade Procedure (not yet implemented)</H3>
<P>
In the future, LON-CAPA will be a versioned system that is released via CD.
The upgrade procedure will be to insert the CD and follow instructions.  The CD
upgrade procedure is already defined and somewhat implemented, but awaits
completion.
</P>
</BODY>
</HTML>
FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>