Scott Harrison
Last updated: 4/18/2001
If you have not yet set yourself up for LON-CAPA CVS, please see the section "Setting yourself up for LON-CAPA CVS".
Before you do a file upgrade, you can always enter a "make statuspost" command to see what will be changing on your system. See the section Viewing the status of your machine.
If you have not yet set yourself up for LON-CAPA CVS, please see the section "Setting yourself up for LON-CAPA CVS".
Assuming that you have set yourself up for LON-CAPA CVS, periodically upgrading your system is a simple process.
| Steps | Commands |
| Make sure you are logged in for CVS | export CVSROOT=:pserver:USERNAME@zaphod.lite.msu.edu:/home/cvs
cvs login |
| Go to your repository directory | cd loncapa |
| Update your CVS sources | cvs update -d |
| Go to the build directory | cd loncom/build |
| Become 'root' | su |
| Install/update static files | make install |
| Install/update dynamically configurable files this preserves the current settings of your machine, don't worry :) |
make configinstall |
| Restart your web server Due to an apache bug, you should enter this command twice. Restarting the web server will
|
/etc/rc.d/init.d/httpd restart
/etc/rc.d/init.d/httpd restart |
| Restart the lonc/lond processes Be patient (this takes several minutes). |
/etc/rc.d/init.d/loncontrol restart |
| After CVS logging in, you can always cut and paste this line
below assuming you do everything as root :) cd loncapa; cvs update -d; cd loncom/build; make install; make configinstall; /etc/rc.d/init.d/httpd restart; /etc/rc.d/init.d/httpd restart; /etc/rc.d/init.d/httpd restart; /etc/rc.d/init.d/loncontrol restart | |
It may be also advisable to test your system after an upgrade if there are critical tasks it is being used for.
There are three things involved in an RPM upgrade: