2. Which one is for me? CVS or RCS

CVS actually uses RCS underneath. CVS is a lot more powerful tool and can control a complete source code tree. It is very strongly recommended that you use CVS, because you can greatly customize CVS with scripting languages like PERL, korn and bash shells. See the sample korn shell scripts at Shell Scripts .

Advantages of CVS

• CVS is de-centralised, user checks out files/directories from the repostitory and has his own seperate stable source directory tree.
• CVS can "STAMP" releases of entire project source tree.
• CVS can enable concurrent editing of files.
• CVS can be greatly customized to enable strong locking of files or enable concurrent editing of files using shell scripts or PERL.

Dis-Advantages of CVS

• Needs little more administration than RCS
• Very highly sophisticated and complex system. It is the "State of the Art" technology.
• Has large number of commands and command options. Hence steeper learning curve for beginners. The shell scripts at Shell Scripts can ease usage.

Advantages of RCS

• RCS is very simple to setup, less administration work.
• RCS is used in a centralized area where everyone works.
• RCS is useful for simple systems.
• Very strong locking of files - concurrency eliminated.

Downside of RCS

• Concurrent development by multiple developers is not possible due to file locking and a single working directory. Because of single working directory, code changes of files by multiple developers can cause failure of 'make' command.
• Cannot stamp releases of entire software project.

This document also has shell scripts which provide simple commands to check-out, check-in, commit files. See shell scripts at Shell Scripts

For RCS see the RCS mini-howto on the linux cdrom -

cd /mnt/cdrom/Redhat/RPMS
ls -l howto-6.0-*.noarch.rpm
rpm -qpl howto-6* | grep -i rcs