From 27f6d5d98dfca86670211a40d3d0f23b57f2834f Mon Sep 17 00:00:00 2001 From: Ben Pfaff Date: Tue, 20 Dec 2005 07:19:43 +0000 Subject: [PATCH] Revising "Setting Up CVS" section. Need to `fs setacl' $HOME also. Add summary of commands. --- doc/devel.texi | 22 +++++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-) diff --git a/doc/devel.texi b/doc/devel.texi index 9a4ed26..ece70a9 100644 --- a/doc/devel.texi +++ b/doc/devel.texi @@ -76,7 +76,14 @@ members access to it. We will assume that the repository will be in a directory called @file{cvs} in the keeper's home directory. First create this directory with @samp{mkdir $HOME/cvs}, then give group members access to it with @samp{fs setacl -dir $HOME/cvs -acl -@var{keeper}:pintos-cvs rlidwk}. +@var{keeper}:pintos-cvs write}. Group members also need to be able to +look up the @file{cvs} directory in the keeper's home directory, which +can be enabled via @samp{fs setacl -dir $HOME -acl +@var{keeper}:pintos-cvs l} (that's letter ``ell,'' not digit +``one.'').@footnote{This command will allow group members to list the +files in your home directory, but not read or write them. It should not +create a security risk unless the names of files in your home directory +are secret.} Now initialize the repository. To initialize the repository, execute @samp{cvs -d $HOME/cvs init}. @@ -92,6 +99,19 @@ command: cvs -d $HOME/cvs import -m "Imported sources" pintos foobar start @end example +Here is a summary of the commands you have now executed: + +@example +pts creategroup @var{keeper}:pintos-cvs +pts adduser -user @var{username} -group @var{keeper}:pintos-cvs +mkdir $HOME/cvs +fs setacl -dir $HOME/cvs -acl @var{keeper}:pintos-cvs write +fs setacl -dir $HOME -acl @var{keeper}:pintos-cvs l +cvs -d $HOME/cvs init +cd /usr/class/cs140/pintos/pintos +cvs -d $HOME/cvs import -m "Imported sources" pintos foobar start +@end example + The repository is now ready for use by any group member, as described below. Keep in mind that the repository should only be accessed using CVS commands---it is not generally useful to examine them by -- 2.30.2