> > > Is there any specific reason why one needs to be able to
> > > write a lock to the CVS repo when running 'make update'
> > > to get a freshly checked out source?
> >
> > Yeah: you aren't running your CVS server in "pserver"
> > mode, and so are trying to do a lock, either in your
> > local copy, or over NFS.
> >
> > If you run your repository in pserver mode, the CVS server
> > will be connected to over the network, instead of attacking
> > your CVS repo directly, and you won't have the problem you
> > are seeing, since the cvs server will be able to get the
> > lock, no problem.
>
> It will also be freakishly slow, and use massive amounts of temp
> space.
No slower than cvs using rsh/ssh, although it does tend to create alot
of inodes in /tmp. (It doesn't create alot of temp space, other than
what is used to create the directories...)
Nate
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
