[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.2 and 1.4

version 1.2, 2000/10/26 07:31:16 version 1.4, 2000/10/26 08:01:26
Line 4 Line 4
 </HEAD>  </HEAD>
 <BODY>  <BODY>
 <H1>LON-CAPA Upgrade</H1>  <H1>LON-CAPA Upgrade</H1>
 <H3>Current Upgrade Procedure (Almost)</H3>  <H3>Current Upgrade Procedure</H3>
 <P>  <P>
 LON-CAPA system releases currently are not released under version  LON-CAPA system releases currently are not released under version
 numbers given the fast pace of system development.  To upgrade your  numbers given the fast pace of system development.  To upgrade your
Line 12  system, you need to Line 12  system, you need to
 <OL>  <OL>
 <LI>Make sure your software packages are up-to-date (based on install.lon-capa.org).  <LI>Make sure your software packages are up-to-date (based on install.lon-capa.org).
 <UL>  <UL>
 <LI>As root, run the script <A HREF="http://install.lon-capa.org/verify/scripts/loncapaverifypackages">  <LI>As root, run the script <TT>/usr/sbin/loncapaverifypackages</TT>.  
 loncapaverifypackages</A>.  This script should be present on your system in the file  If packages are out-of-date, this script will output
 /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",  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  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  may represent important modifications of your institution, so do with care.  Removing
Line 24  packages is done with the command: <TT>r Line 23  packages is done with the command: <TT>r
 <UL>  <UL>
 <LI>Upgrade software packages by either  <LI>Upgrade software packages by either
 <UL>  <UL>
 <LI>Running /usr/sbin/<A HREF="http://www.lon-capa.org/install/verify/scripts/loncapaupgradepackages">loncapaupgradepackages</A>.  <LI>Running <TT>/usr/sbin/loncapaupgradepackages</TT>.
 <LI>Or, going to <A HREF="http://www.lon-capa.org/install/RPMS/">http://www.lon-capa.org/install/RPMS/</A>,  <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 individual download each package from the world-wide web.  You then need to enter the command:  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.  <TT>rpm -Uvh --force PACKAGE_RPM_FILE_NAME</TT> to upgrade your system for each package.
 </UL>  </UL>
 </UL>  </UL>
   <LI>Make the LON-CAPA base files up to date (based on install.lon-capa.org).
   <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>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.
   </UL>
 <LI>Restore configuration files.  <LI>Restore configuration files.
 <UL>  <UL>
 <LI>As you run /usr/sbin/loncapaupgradepackages or enter in <TT>rpm -Uvh --force</TT> commands, you may  <LI>As you run /usr/sbin/loncapaupgradepackages or enter in <TT>rpm -Uvh --force</TT> commands, you may
Line 40  see messages appear on your screen such Line 46  see messages appear on your screen such
 <BR>to restore your configurations.  However, it is worthwhile to use the 'diff' command  <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  to make sure that you are not accidentally losing important updates to the configuration
 files.    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.  <LI>Alternatively, you can run <TT>/usr/sbin/loncaparestoreconfigurations</TT> to "smartly" run through the system and restore LON-CAPA configuration values.
   </UL>
   <LI>Restart the LON-CAPA networking processes
   <UL>
   <LI><TT>/etc/rc.d/init.d/loncontrol restart</TT>
 </UL>  </UL>
 <LI>Should you wish to automate all of this, you can (at your own risk) enable a script which will  <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.  <B>This definitely should NOT be implemented on a system that students  do all of this automatically.  You can run this script by entering the command:
 are using)</B>.  You can enable this script by entering the command:  <TT>/usr/sbin/loncapaautoupgrade</TT>
 <TT>cp /usr/sbin/<A HREF="http://www.lon-capa.org/install/verify/scripts/loncapaautoupgrade">loncapaautoupgrade</A> /etc/cron.daily/loncapaautoupgrade</TT>  
 </OL>  </OL>
 </P>  </P>
 <H3>Future Upgrade Procedure (not yet implemented)</H3>  <H3>Future Upgrade Procedure (not yet implemented)</H3>
Removed from v.1.2  
changed lines
  Added in v.1.4

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