File permissions -- CVS---Concurrent Versions System
Up: User modules
Top: Top
4.1.1. File permissions
All `,v' files are created read-only, and you
should not change the permission of those files. The
directories inside the repository should be writable by
the persons that have permission to modify the files in
each directory. This normally means that you must
create a UNIX group (see group(5)) consisting of the
persons that are to edit the files in a project, and
set up the repository so that it is that group that
owns the directory.
This means that you can only control access to files on
a per-directory basis.
cvs tries to set up reasonable file permissions
for new directories that are added inside the tree, but
you must fix the permissions manually when a new
directory should have different permissions than its
parent directory.
Since cvs was not written to be run setuid, it is
unsafe to try to run it setuid. You cannot use the
setuid features of rcs together with cvs.
Up: User modules
Top: Top