Chris Cowan <[EMAIL PROTECTED]> writes:
> In the past (no longer), I've used or attempted to used RCS and CVS with
> both AFS and DFS. (I admined AFS for over 6 years, DFS for 2 years). I
> would avoid the AFS/CVS combination for the following reasons:
I've been using CVS with AFS for years now and it works great. It's a bit
slower than having a repository on local disk, but ease of backups and
universal accessibility more than makes up for it.
> - AFS (unlike DFS) does not support any sort file locking in the
> "normal" (POSIX) manner. Even if you enable the "k" ACL on the
> directory!
Irrelevant for CVS, which uses dot-locking that works fine in AFS.
> - It is not trivial to properly set up AFS ACLs so that you get the
> correct permissions and access by all parties using the CVS repository.
> It may not be possible!
It's trivial. Give everyone who needs to commit to a tree "write" access
to all directories in that tree, give everyone "read" access to CVSROOT,
and create a subdirectory of CVSROOT (I call it logs), give everyone
"write" access to it, move the history and val-tags files into it, and
symlink to the files.
> - Many users of AFS get very confused by the difference between RO and
> RW volumes. Typically, this is done with mount points. This is usually
> differentiated by using /afs/.iil instead of /afs/ill. I would be
> absolutely sure that your CVS repository does not sit in any replicated
> volumes. If so, make sure you're accessing the RW copy.
Don't replicate your CVS repository, other than the top-level mount point
volume if you use that sort of scheme. You should in general never
replicate development trees; replication is for mostly static data that
needs to always be available.
> - The recursion you're seeing "smells" like a backup volume somewhere.
> Depending upon where the backup volume is mounted, this could cause some
> interesting problems.
Don't mount backup volumes unless you're actually using them. There's no
reason to.
> Bottom line, I would follow the advice of the other person that replied.
> Use CVS in client/server mode or use a remote filesystem that can handle
> the POSIX functionality upon which CVS depends, like DFS or NFS (w/ the
> lock manager).
I couldn't disagree more strongly; that's horrible advice. CVS works
great on AFS.
>> Now, I'm doing something weird:
>> cvs -d /afs/iil/nike/data/fcde/cvsroot co pvpd_utils/src/..
Don't do that. The .. directory is confusing CVS and that's causing the
rest of your problems. I bet you could create this same problem in other
file systems as well.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
