[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.1 and 1.7

version 1.1, 2000/10/25 18:37:49 version 1.7, 2002/04/23 11:55:11
Line 1 Line 1
 <HTML>  <html>
 <HEAD>  <head>
 <TITLE>LON-CAPA Upgrade</TITLE>  <title>LON-CAPA Upgrade</title>
 </HEAD>  <!-- pdfahref upgrade.pdf -->
 <BODY>  <!-- button UPGRADE -->
 <H1>LON-CAPA Upgrade</H1>  </head>
 <H3>Current Upgrade Procedure (Almost)</H3>  <body>
 <P>  <!-- preamble start -->
   <h1>LON-CAPA Upgrade</h1>
   <h3>Current Upgrade Procedure</h3>
   <!-- preamble end -->
   <!-- maintext start -->
   <p>
   Scott Harrison
   </p>
   <p>
   Last updated: 4/18/2001
   </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
 system, you need to   system, you need to 
 <OL>  <ol>
 <LI>Make sure your software packages are up-to-date (based on www.lon-capa.org).  <li>Make sure your software packages are up-to-date
 <UL>  (based on install.lon-capa.org).</li>
 <LI>As root, run the script <A HREF="http://www.lon-capa.org/install/verify/scripts/loncapaverifypackages">  <ul>
 loncapaverifypackages</A>.  This script should be present on your system in the file  <li>As root, run the script <tt>/usr/sbin/loncapaverifypackages</tt>.  
 /usr/sbin/loncapaverifypackages.  If packages are out-of-date, this script will output  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
 are packages that you may wish to remove to improve system security.  (These packages  "should not be here", are packages that you may wish to remove to
 may represent important modifications of your institution, so do with care.  Removing  improve system security.  (These packages may represent important
 packages is done with the command: <TT>rpm -e --nodeps PACKAGE_NAME</TT>.  modifications of your institution, so do with care.  Removing
 </UL>  packages is done with the command: <tt>rpm -e --nodeps PACKAGE_NAME</tt>.</li>
 <LI>Upgrade old software packages.  </ul>
 <UL>  <li>Upgrade old software packages.</li>
 <LI>Upgrade software packages by either  <ul>
 <UL>  <li>Upgrade software packages by either</li>
 <LI>Running /usr/sbin/<A HREF="http://www.lon-capa.org/install/verify/scripts/loncapaupgradepackages">loncapaupgradepackages</A>.  <ul>
 <LI>Or, going to <A HREF="http://www.lon-capa.org/install/RPMS/">http://www.lon-capa.org/install/RPMS/</A>,  <li>Running <tt>/usr/sbin/loncapaupgradepackages</tt>.</li>
 you can individual download each package from the world-wide web.  You then need to enter the command:  <li>Or, going to <a href="http://install.lon-capa.org/3.1/SupplementalRPMS/">http://install.lon-capa.org/3.1/SupplementalRPMS/</a>,
 <TT>rpm -Uvh --force PACKAGE_RPM_FILE_NAME</TT> to upgrade your system.  you can individually download each package from the world-wide web.  You 
 </UL>  then need to enter the command:
 </UL>  <tt>rpm -Uvh --force PACKAGE_RPM_FILE_NAME</tt> to upgrade your system
 <LI>Restore configuration files.  for each package.</li>
 <UL>  </ul>
 <LI>As you run /usr/sbin/loncapaupgradepackages or enter in <TT>rpm -Uvh --force</TT> commands, you may  </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:  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 /><tt>warning: /etc/httpd/conf/access.conf saved as
 <BR>You can probably just type in commands like:  /etc/httpd/conf/access.conf.rpmsave</tt>
 <BR><TT>cp /etc/httpd/conf/access.conf.rpmsave /etc/httpd/conf/access.conf</TT>  <br />You can probably just type in commands like:
 <BR>to restore your configurations.  However, it is worthwhile to use the 'diff' command  <br /><tt>cp /etc/httpd/conf/access.conf.rpmsave
 to make sure that you are not accidentally losing important updates to the configuration  /etc/httpd/conf/access.conf</tt>
 files.    <br />to restore your configurations.  However, it is worthwhile to use the
 <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.  'diff' command to make sure that you are not accidentally losing important
 </UL>  updates to the configuration files.  
 <LI>Should you wish to automate all of this, you can (at your own risk) enable a script which will  <li>Alternatively, you can run <tt>/usr/sbin/loncaparestoreconfigurations</tt>
 do all of this automatically.  <B>This definitely should NOT be implemented on a system that students  to "smartly" run through the system and restore LON-CAPA configuration
 are using)</B>.  You can enable this script by entering the command:  values.</li>
 <TT>cp /usr/sbin/<A HREF="http://www.lon-capa.org/install/verify/scripts/loncapaautoupgrade">loncapaautoupgrade</A> /etc/cron.daily/loncapaautoupgrade</TT>  </ul>
 </OL>  <li>Restart the LON-CAPA networking processes
 </P>  <ul>
 <H3>Future Upgrade Procedure (not yet implemented)</H3>  <li><tt>/etc/rc.d/init.d/loncontrol restart</tt></li>
 <P>  </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>
   <h3>Future Upgrade Procedure (not yet implemented)</h3>
   <p>
 In the future, LON-CAPA will be a versioned system that is released via CD.  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  The upgrade procedure will be to insert the CD and follow instructions.  The CD
 upgrade procedure is already defined and somewhat implemented, but awaits  upgrade procedure is already defined and somewhat implemented, but awaits
 completion.  completion.
 </P>  
 </BODY>  
 </HTML>  
   
   </p>
   <!-- maintext end -->
   </body>
   </html>
Removed from v.1.1  
changed lines
  Added in v.1.7

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