Les,
> The point remains that if they have write access through mapped files, >> they have the capability of destroying everything there. >> >> You could probably whip up a cgi script to create new repositories from a >> web request form if something like that doesn't already exist. Or you could >> put more than one project inside a single repository so all you have to do >> is create a new top level directory with the trunk/branches/tags structure >> under it. There are some downsides, but it is not an unreasonable approach >> and it lets users do everything remotely. > > I do undestand your concern but in our case we don't have any option other than putting repositories on the network drives. Let's just say our hands are tied. Having just a top level repository is also not viable in our case. We need one repository per project. My only other option now is to try upgrading the SVN server on the Linux machine...
