[EMAIL PROTECTED] (Greg A. Woods) writes: > If I had any say in sourceforge I'd encourage them to move read-only > anonymous access over to a separate non-trusted system that cannot write > to the live repositories (they could do this either with NFS and a > couple of tiny hacks, or with regular CVSup updates, etc.) and I'd > further encourage them to ditch cvspserver support entirely and set up > unique (i.e. per-project) anonymous SSH accounts for read-only access. What would be wrong with them running the anonymous access as a dedicated "nobody" user (i.e. no write access to anything in the repository) with the lockfiles written out into a separate directory tree? -- James Youngman Manchester, UK. +44 161 226 7339 PGP fingerprint <[EMAIL PROTECTED]> = 0C1CD7CA6633D2E914E05F16D52460E9
- Re: patch to make CVS chroot Larry Jones
- Re: patch to make CVS chroot Justin Wells
- Re: patch to make CVS chroot Larry Jones
- Re: patch to make CVS chroot Justin Wells
- Re: patch to make CVS chroot Greg A. Woods
- Re: patch to make CVS chroot Justin Wells
- Re: patch to make CVS chroot Tobias Weingartner
- Re: patch to make CVS chroot Justin Wells
- Re: patch to make CVS chroot Alexey Mahotkin
- Re: patch to make CVS chroot Greg A. Woods
- Re: patch to make CVS chroot James Youngman
- Re: patch to make CVS chroot Greg A. Woods
- Re: patch to make CVS chroot Mark Harrison
- Re: patch to make CVS chroot Greg A. Woods
- Re: patch to make CVS chroot Justin Wells
- Re: patch to make CVS chroot Greg A. Woods
- Re: patch to make CVS chroot Greg A. Woods
- Re: patch to make CVS chroot Justin Wells
- Re: patch to make CVS chroot Greg A. Woods
- Re: patch to make CVS chroot Justin Wells
- Re: patch to make CVS chroot Alexey Mahotkin