Re: chmod and DOS vs POSIX paths

http://cygwin.com/acronyms/#TOFU On Jan 25 11:25, brassrat wrote: > > I agree that the having an R/O attribute conflicts with the concept of ACLS; > however, it is not true that the chmod command does not change this flag. > For example, > if you chmod +w a file with the R/O flag 'set' the R/O

Re: chmod and DOS vs POSIX paths

ll not return to set the flag in calls to chmod. The official workaround is, use the Windows attrib command. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- View this message in con

Re: chmod and DOS vs POSIX paths

On Jan 25 07:55, brassrat wrote: > > 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 > fort

chmod and DOS vs POSIX paths

it make sense for something like: chmod ugo-w DIR/FILE to set it? -- View this message in context: http://old.nabble.com/chmod-and-DOS-vs-POSIX-paths-tp27307971p27307971.html Sent from the Cygwin list mailing list archive at Nabble.com. -- Problem reports: http://cygwin.com/problems