Alright, I've got a nasty legacy environment setup.
Users develop cold fusion code on Windows desktops. They use SVN (With Tortoise as their client) to check out code. They check out directly to a Samba share off of the development ColdFusion machine, and RedHat box. All the desktops use the same Linux user to map the drive. That share is, itself, not physically hosted on the Dev box, but is a NFS share from a NetApp filer.
Ugh.
All this, believe it or not, was working fine until an upgrade to Windows 7. Now the users cannot delete checked out folders, because the entries file inside the checkout is marked as Read Only. The user who the clients map the drive as have permissions to change the permissions on this file, and Windows XP would silently delete the file, no fuss, no muss. Windows 7 alerts that the user needs to map the drive as the user which they are already using.
A similar problem occurs when users rename files in their local copy. They can check in fine, but then Tortoise complains about the local copy being corrupt. It seems like this is the same issue.
I'm a Linux admin, and am lacking some of the cross-domain knowledge to solve this one.
1) If I set permissions to 644 recursively it seems to resolve the trouble. Does anyone know if this will break the Tortoise client in any way?
2) Is there a Windows change that might allow reversion to the XP behavior, at least in this particular case?
