X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=1.9 required=5.0 	tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By: sourceware.org
Message-ID: <27307971.post@talk.nabble.com>
Date: Mon, 25 Jan 2010 07:55:21 -0800 (PST)
From: brassrat <work AT mgjg DOT com>
To: cygwin AT cygwin DOT com
Subject: chmod and DOS vs POSIX paths
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com


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 'DIR\FILE' (or chmod -w
$(cygpath -w DIR/FILE))
i.e., using a DOS path makes cygwin treat the file system as not having acls
and i guess that kicks in the old behavior.

Is this the only way to change the 'read-only' attribute on windows files?
Would 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.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple