CVS directories are up, and available a in /home/solaris/ieng9/cs120f/public/cvs/groupXX where XX ranges from 1-39, and is your group number, as found in http://b5.ucsd.edu/~clucas/cse120/groups.txt Only one person in the group should initialize the CVS repository and import your initial code. To do this, follow the following steps: 1. set the CVSROOT environmental variable to your cvs directory, ie setenv CVSROOT /home/solaris/ieng9/cs120f/public/cvs/group3 or if you use bash export CVSROOT=/home/solaris/ieng9/cs120f/public/cvs/group3 2. type 'cvs init' to initialize the repository 3. This is very important, change to the directory you want to import, ie cd ~/Nachos-3.4 4. type 'cvs import <full directory path from home> my_vendor release_0' For example, in the above case, this would be cvs import Nachos-3.4 my_vendor release_0 The vendor and release tags are basically almost anything you want. Once this is done, anyone in the group should be able to use the CVS commands on the repository. Before you do any commands, make sure to set CVSROOT as described in step 1 above, then the following commands are useful. So... setenv CVSROOT /home/solaris/ieng9/cs120f/public/cvs/group3 (this could easily go in your .cshrc file if you get tired of typing it) and then... - cvs checkout nachos-3.4 You need to do this at least once in order to get the current version out of CVS. If you already have a directory named nachos-3.4 with the source code, it won't work, because it doesn't have the CVS information, in which case it'd be best to move that to another directory and start fresh with your CVS copy. - cvs commit commits changes in the current directory tree. It will find any files that have changed, and will let you give a message indicating what you did. Each version of the file will be saved, and can be retrieved if need be. Note that by default you will be using vi to edit this information, if you would like to use a different editor, set the CVSEDITOR environment variable to the editor you would like to use (probably emacs, so setenv CVSEDITOR emacs or export CVSEDITOR=emacs). You may get an error saying that the up-to-date check failed, in which case you should update before committing (see below). - cvs update -A Updates the code to the latest version from the archive, will merge in changes if your partners and you have both changed the same files, this usually is okay, but if there is a problem, you will have to edit it manually, as it will put strange messages in your code that cause it to not compile anymore. - cvs rtag . Labels the current code by a tag specified in the command line. You can then use this tag to keep track of older versions of the code. This is mostly useful for labeling the code when you are done as the turned in code. If you label it and then want to label it using the same tag again, use cvs rtag -F . - cvs add Adds a file to the CVS repository - cvs remove Remove a file from the CVS repository, the file must be deleted on the local system as well. You probably should remove binaries such as 'nachos' from the repository, as CVS doesn't work very well with binaries. There are many more commands, but these should get you started. CVS's builtin help is very informative about any other commands you may be interested in.