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</h3>
8: <p>
9: Scott Harrison
10: </p>
11: <p>
12: Last updated: 4/18/2001
13: </p>
14: <p>
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>
19: <li>Make sure your software packages are up-to-date
20: (based on install.lon-capa.org).</li>
21: <ul>
22: <li>As root, run the script <tt>/usr/sbin/loncapaverifypackages</tt>.
23: If packages are out-of-date, this script will output
24: the out-of-date packages. Packages that this script identifies as
25: "should not be here", are packages that you may wish to remove to
26: improve system security. (These packages may represent important
27: modifications of your institution, so do with care. Removing
28: packages is done with the command: <tt>rpm -e --nodeps PACKAGE_NAME</tt>.</li>
29: </ul>
30: <li>Upgrade old software packages.</li>
31: <ul>
32: <li>Upgrade software packages by either</li>
33: <ul>
34: <li>Running <tt>/usr/sbin/loncapaupgradepackages</tt>.</li>
35: <li>Or, going to <a href="http://install.lon-capa.org/3.1/SupplementalRPMS/">http://install.lon-capa.org/3.1/SupplementalRPMS/</a>,
36: you can individually download each package from the world-wide web. You
37: then need to enter the command:
38: <tt>rpm -Uvh --force PACKAGE_RPM_FILE_NAME</tt> to upgrade your system
39: for each package.</li>
40: </ul>
41: </ul>
42: <li>Make the LON-CAPA base files up to date (based on
43: install.lon-capa.org).</li>
44: <ul>
45: <li><B>[optional]</B> Run the script
46: <tt>/usr/sbin/loncapaverifybasepackage</tt>. Then view
47: /home/httpd/html/dev/index.html for the verification report.
48: If there are no real changes, then you do not need to make your files
49: up-to-date.</li>
50: <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">
51: 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>
52: </ul>
53: <li>Restore configuration files.</li>
54: <ul>
55: <li>As you run /usr/sbin/loncapaupgradepackages or enter in
56: <tt>rpm -Uvh --force</tt> commands, you may
57: see messages appear on your screen such as:
58: <br /><tt>warning: /etc/httpd/conf/access.conf saved as
59: /etc/httpd/conf/access.conf.rpmsave</tt>
60: <br />You can probably just type in commands like:
61: <br /><tt>cp /etc/httpd/conf/access.conf.rpmsave
62: /etc/httpd/conf/access.conf</tt>
63: <br />to restore your configurations. However, it is worthwhile to use the
64: 'diff' command to make sure that you are not accidentally losing important
65: updates to the configuration files.
66: <li>Alternatively, you can run <tt>/usr/sbin/loncaparestoreconfigurations</tt>
67: to "smartly" run through the system and restore LON-CAPA configuration
68: values.</li>
69: </ul>
70: <li>Restart the LON-CAPA networking processes
71: <ul>
72: <li><tt>/etc/rc.d/init.d/loncontrol restart</tt></li>
73: </ul>
74: <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
75: do all of this automatically. You can run this script by entering the command:
76: <TT>/usr/sbin/loncapaautoupgrade</TT></li>
77: </ol>
78: </p>
79: <h3>Future Upgrade Procedure (not yet implemented)</h3>
80: <p>
81: In the future, LON-CAPA will be a versioned system that is released via CD.
82: The upgrade procedure will be to insert the CD and follow instructions. The CD
83: upgrade procedure is already defined and somewhat implemented, but awaits
84: completion.
85: </p>
86: </body>
87: </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