CVS_SETTING_UP.INF
Creating a repository:
---------------------

> cvs -d /nstxusr1/cvsroot_trg init

  This creates both

      /nstxusr1/cvsroot_trg (if required)
          the CVSROOT directory:  "setenv CVSROOT /nstxusr1/cvsroot_trg"

      /nstxusr1/cvsroot_trg/CVSROOT.
          contains bookkeeping files for the entire repository.

  NOTE: the repository can include many different "modules";  each
  can be independently maintained.

Importing an entire directory:
-----------------------------

To import the directory ~/psc as a new module in the repository:

  > cd ~/psc

  > cvs import -m'Import psc from remote node'   psc  psc  PSC_0_01
        or
  > cvs import -m'Import psc into cvs'  $CVSROOT/psc  psc  PSC_0_01
                                            /         /      /
                             New CVS directory       /      /
                                              Vendortag    /
                                                      Releasetag
    The "Vendortag" and "Releasetag" are pretty much ignored, but are
    required by cvs.


Exporting a module:
------------------
This operation creates a complete set of files in the specified user
directory.  You can then "tar" the directory, or whatever.


  > cvs export -r PSC_0_02 [ -d ~/woof ] psc
      - or -
  > cvs export -D date(e.g. "today") [ -d ~/woof ] psc

    If "-d" not specified, then directory "psc" is created under cwd.

  > cd ~
  > tar cf woof.tar woof


File protection:
---------------
Most likely done via "group" privilege.
To allow a user to checkout a module, he must have "w" privilege on
  o All directories, in order to create temporary "locks"
  o $CVSROOT/CVSROOT/history

This *may* not be necessary if you're only "export"ing the module?