There are ways around this. Kerberos, ssh and chroot are your friends
:-)
: Someone please correct me if I don't have my facts straight, but as
: I understand it, it is OpenBSD, not NetBSD that has the 'anoncvs'
: tree.
OpenBSD has the anoncvs tree. FreeBSD allows you to sup copies of the
CVS tree. NetBSD has a CVS tree for developers. All three you need
special permissions to actually check code into the tree. All three
have people with commit privs that will general commit good patches
promptly.
Right now I don't see what having an unofficial CVS tree available
over the net would buy us (the whole Linux community). I do see
utility in this for, say, the MIPS or Sparc or Alpha or PPC or
whatever ports that are going on. However, it up to those port
coordinators to actually do this or not do this.
The real win in *BSD, imho, is that the whole core system is in the
CVS tree: compilers, kernel, libc, utilities, etc. It makes it easier
for them to maintain two branches of the OS (in FreeBSD's case) for
long periods of time of "active" development in both.
Anyway, source code control is a religious issue. I'm reporting
something that works well for others. I don't know if the dynamics of
this situation would warrant a similar direction or not.
Warner