Re: chmod and DOS vs POSIX paths

2010-01-25 Thread brassrat
7;t setting the 'r/o flag' (if supported by the underlying file system) capture this concept better than some combination of acl entries? Given the various workarounds, this is not a significant issue, but it surprised me when scripts that i have had working for years stopped working. O

chmod and DOS vs POSIX paths

2010-01-25 Thread brassrat
The source control package i use at work is sensitive to the 'read-only' attribute of Windows files. prior to 1.7, the command 'chmod -w DIR/FILE' worked fine. now, with 1.7, chmod -w FILE no longer sets the read-only attribute - i guess because fortunately, there is a 'work-around': chmod -w 'DI