CVS allows for the same file to be worked on by two different people at the same time. The second person to return the file to repository has their changes deferred. He or she must execute the update command whereby the cvs program institutes the update to the file(s) unless both programers have made changes to the same part of the file. In that case, the second programmer must resolve the conflicts.
CVS is and excellent too for collaborations on programs, scripts, or even as a backup assistance. But note that due to the nature of cvs, there are certain files that must be handled with care when included in cvs repositories. Binary files, images, etc. must be added differently than text files and scripts so that their integrity is intact throughout the entire process. This will be discussed later.
cvs -d thelinuxlink.net:/storage/cvs checkout lvlug
cvs commit lvlug
The Repository is where the cvs file are stored; either locally or on a remote machine. The repository is typically created by the cvs administrator issuing the cvs import command.
The Sandbox refers to the directory(ies) holding the cvs user's current session of files. The user typically designates a directory; possibly underneath their home directory; for the Sandbox files. Once this directory is created the user issues the cvs checkout command to retrieve the files from the cvs repository.
Module is the name of the dirctory holding the specific cvs repository files. For instance, if I created a cvs repository of the lvlug the module name would be lvlug. The module name of the cvsdemo files.