SSL home page

CVS Basics


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/cvs 
Where <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/emacs
so 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_profile
in order to get the environment variables into your current environment. Nothing will work until you do this.


Basic CVS commands

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:

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.