Date: Mon, 25 Jan 2010 17:05:34 +0100
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: chmod and DOS vs POSIX paths
Message-ID: <20100125160534.GO2402@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <27307971.post@talk.nabble.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <27307971.post@talk.nabble.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

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 
> 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?

The R/O attribute is really in the way on filesystems supporting ACLs
due to the way it's implemented.  Therefore, no, Cygwin will 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

--
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