X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 	tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: sourceware.org
Message-ID: <4B46431E.7050101@fastmail.fm>
Date: Thu, 07 Jan 2010 15:25:02 -0500
From: Raman Gupta <rocketraman AT fastmail DOT fm>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.1.5) Gecko/20091130 Lightning/1.0b2pre Thunderbird/3.0
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: 1.7.1-1 noacl on samba share has incorrect directory write bit
References: <4B454550 DOT 9020806 AT fastmail DOT fm>  <4B454E96 DOT 7060009 AT cygwin DOT com>  <4B45739C DOT 4060807 AT fastmail DOT fm>  <20100107180214 DOT GP23972 AT calimero DOT vinschen DOT de>  <4B462AFD DOT 8030809 AT fastmail DOT fm>  <20100107195022 DOT GQ23972 AT calimero DOT vinschen DOT de>  <4B463D68 DOT 1070906 AT fastmail DOT fm> <20100107200946 DOT GR23972 AT calimero DOT vinschen DOT de>
In-Reply-To: <20100107200946.GR23972@calimero.vinschen.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
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

On 01/07/2010 03:09 PM, Corinna Vinschen wrote:
> On Jan  7 15:00, Raman Gupta wrote:
>> On 01/07/2010 02:50 PM, Corinna Vinschen wrote:
>>> On Jan  7 13:42, Raman Gupta wrote:
>>>> In any case, note that the KB article says that attrib *can* be used
>>>> to see and modify the value -- as I demonstrated in my previous
>>>> email.
>>>
>>> Sure.  That has nothing to do with what I'm talking about.  While you
>>> can set and reset the R/O bit on a dir, it doesn't have the *meaning* of
>>> the directory being R/O.  If Cygwin reports such a directory as being
>>> read-only from the POSIX perspective, certain functions would have
>>> strange ideas and return EACCES, for instance.
>>
>> In the case I am speaking of (a Samba share using the default
>> settings), the functions *should* return EACCES, since on the
>> server-side the directory is indeed non-writable.
>
> I'm talking about the other case.  The DOS R/O flag has nothing to do
> with writability of a directory in the first place.  If we treat a
> directory as non-writable just because the DOS R/O flag is set, we're
> making a mistake with consequences.  The consequences in the opposite
> case are much less problematic.

Right -- which is why I suggested gating this using a "dro/nodro" 
attribute so that it could be turned on by users of noacl samba mounts 
where it would be correct to turn it on -- I suspect noacl samba 
mounts are widely used and would benefit greatly from this as EACCES 
would be correctly returned in many situations in which it currently 
isn't.

Since nodro (i.e. current behavior) would remain the default, there 
should be no negative consequences.

Cheers,
Raman

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