Re: svn not atomic with file:/// access?

Ignacio González T. wrote:
>
>> i do appreciate all the concern for my environment but any chance
>> someone can answer my actual question, namely what weird things can
>> happen with file:/// ? I'm just interested to know what the mechanics
>> of this are. is the only issue that file:/// leaves the repos wide
>> open for deletion on the file-system?
>
> My two (Euro)cents:
>
> The main reason we swicthed from rcs (yes, bare rcs) to subversion was to avoid
> repository corruption associated with file:///-like access inherent to our
> development environment: Windows machines using a Windows-server directory
> as repository, mapped as a unit drive.
>
> This environment worked quite well for years, until we had to use it remotely from
> another site. In this situation, network connections were more likely to fail, AND
> we began to notice repository corruption.
>
> We had to mentally adjust from the one-file-at-a-time-based, prelocking-based
> way to the system-wide-based, merging-base way, but, as hard as it resulted, it
> was worth while.

If you _wanted_ file-at-a-time access with rcs under the covers, CVS
with pserver access might have been an easier transition. Most people
like the atomic directory/project actions in subversion better, though.

-- 
   Les Mikesell
    lesmikesell_at_gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org