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