Annotation of doc/build/upgrade.html, revision 1.2
1.1 harris41 1: <HTML>
2: <HEAD>
3: <TITLE>LON-CAPA Upgrade</TITLE>
4: </HEAD>
5: <BODY>
6: <H1>LON-CAPA Upgrade</H1>
7: <H3>Current Upgrade Procedure (Almost)</H3>
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.2 ! harris41 15: <LI>As root, run the script <A HREF="http://install.lon-capa.org/verify/scripts/loncapaverifypackages">
1.1 harris41 16: loncapaverifypackages</A>. This script should be present on your system in the file
17: /usr/sbin/loncapaverifypackages. If packages are out-of-date, this script will output
18: the out-of-date packages. Packages that this script identifies as "should not be here",
19: are packages that you may wish to remove to improve system security. (These packages
20: may represent important modifications of your institution, so do with care. Removing
21: packages is done with the command: <TT>rpm -e --nodeps PACKAGE_NAME</TT>.
22: </UL>
23: <LI>Upgrade old software packages.
24: <UL>
25: <LI>Upgrade software packages by either
26: <UL>
27: <LI>Running /usr/sbin/<A HREF="http://www.lon-capa.org/install/verify/scripts/loncapaupgradepackages">loncapaupgradepackages</A>.
28: <LI>Or, going to <A HREF="http://www.lon-capa.org/install/RPMS/">http://www.lon-capa.org/install/RPMS/</A>,
29: you can individual download each package from the world-wide web. You then need to enter the command:
30: <TT>rpm -Uvh --force PACKAGE_RPM_FILE_NAME</TT> to upgrade your system.
31: </UL>
32: </UL>
33: <LI>Restore configuration files.
34: <UL>
35: <LI>As you run /usr/sbin/loncapaupgradepackages or enter in <TT>rpm -Uvh --force</TT> commands, you may
36: see messages appear on your screen such as:
37: <BR><TT>warning: /etc/httpd/conf/access.conf saved as /etc/httpd/conf/access.conf.rpmsave</TT>
38: <BR>You can probably just type in commands like:
39: <BR><TT>cp /etc/httpd/conf/access.conf.rpmsave /etc/httpd/conf/access.conf</TT>
40: <BR>to restore your configurations. However, it is worthwhile to use the 'diff' command
41: to make sure that you are not accidentally losing important updates to the configuration
42: files.
43: <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.
44: </UL>
45: <LI>Should you wish to automate all of this, you can (at your own risk) enable a script which will
46: do all of this automatically. <B>This definitely should NOT be implemented on a system that students
47: are using)</B>. You can enable this script by entering the command:
48: <TT>cp /usr/sbin/<A HREF="http://www.lon-capa.org/install/verify/scripts/loncapaautoupgrade">loncapaautoupgrade</A> /etc/cron.daily/loncapaautoupgrade</TT>
49: </OL>
50: </P>
51: <H3>Future Upgrade Procedure (not yet implemented)</H3>
52: <P>
53: In the future, LON-CAPA will be a versioned system that is released via CD.
54: The upgrade procedure will be to insert the CD and follow instructions. The CD
55: upgrade procedure is already defined and somewhat implemented, but awaits
56: completion.
57: </P>
58: </BODY>
59: </HTML>
FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>
![[BACK]](/icons/back.gif){kind=icon}
Return to upgrade.html CVS log ![[TXT]](/icons/text.gif){kind=icon}
![[DIR]](/icons/dir.gif){kind=icon}
Up to [LON-CAPA] / doc / build