The acenic firmware now resides in a cvs archive on jemez.cs.unm.edu. In order to use it, you will first need to set up some defaults in your account.
Edit your .bash_profile account (assuming the box is running linux
and using the bash shell. For other OSes and shells, see the CVS HOWTO
or ask todd). Add the following
line:
export CVSROOT=:pserver:<username>@jemez.cs.unm.edu:/usr/local/cvsWhere <username> is your username on jemez. Currently only patricia, todd and wenbin have access to the cvs archive, but others could use this as necessary. Note that it is actually very important to add this exactly as written, in particular to leave the trailing slash ('/') off of the /usr/local/cvs.
You may also choose to add:
export EDITOR=/usr/bin/emacsso that you don't have to use that horrible vi editor! You could also choose any other editor you might want to use.
After you've made these changes, be sure to either re-log-in or just execute
. ~/.bash_profilein order to get the environment variables into your current environment. Nothing will work until you do this.
CVS will do almost everything you want but there are really only a few kinds of things that you should ever need to do with cvs for this project:
cvs loginYou will need to do this in order to be able to access the remote archive on jemez. This will only work if you set your $CVSROOT variable as described above. You are following directions, aren't you?
cvs checkout acenicThis will make a copy of the entire acenic archive in a subdirectory of your current directory called (not surprisingly) 'acenic'.
cvs update acenicor
cvs update <filename>This fetches a new copy of the file or whole archive and merges your local changes with any changes to the archive copy since you last checked it out. Changes to different regions of the file do not cause conflicts but changes to similar regions will result in commented sections that are mutually exclusive. CVS will warn you if this happens.
cvs commit <filename>This will try to commit your file back into the archive. If there have been changes since you last checked it out, you will need to to a 'cvs update' (see above), resolve any conflicts and try to commit again.
cvs add <filename>This adds the file names <filename> as a new file to the archive (it its current location in the directory hierarchy). This should be rare for us.
Keep in mind that cvs is not like rcs in some important ways: files are almost never locked in cvs. Each user has a local copy that they can modify as they choose. Changes to the local copies are only resolved upon 'commit' operations.
That should be all you need to know to use the firmware archive through cvs.