X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 	tests=AWL,BAYES_00
X-Spam-Check-By: sourceware.org
X-Authority-Analysis: v=1.0 c=1 a=eLZWO0hulmsA:10 a=mlLn1eFFB4sA:10  a=w_pzkKWiAAAA:8 a=KatdleRcQEMbPEzQ_SUA:9 a=YDkYKbb94Abrhf2ihAkA:7  a=9J5VCfuj0syOlfOS6oy5jcSzRCkA:4 a=66msUWWtX2wA:10 a=MxZ3bB5I4kYA:10  a=G2AsRb49nnwmWARIy9zzNStElGQ=:19
X-CM-Score: 0.00
Message-ID: <494C245F.4060003@i12.com>
Date: Fri, 19 Dec 2008 14:46:55 -0800
From: Lawrence Mayer <lawmay3 AT i12 DOT com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9.1b3pre) Gecko/20081204 Thunderbird/3.0b1
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Re: noacl functionality for MS-DOS destination paths?
References: <20081219114543 DOT GA24117 AT calimero DOT vinschen DOT de>
In-Reply-To: <20081219114543.GA24117@calimero.vinschen.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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 Dec 18 20:53, Lawrence Mayer wrote:
>> Is there any way to get noacl functionality when using MS-DOS destination
>> paths?
>>
>> My etc/fstab file (below) applies noacl for UNIX destination paths e.g.
>>
>> C:\cygwin\bin\mkdir.exe /c/foo
>>
>> creates directory C:\foo with NTFS default permissions inherited from
>> parent directory C:\ (the same as DOS mkdir C:\foo would do).
>>
>> But an MS-DOS destination path, e.g.
>>
>> C:\cygwin\bin\mkdir.exe C:\foo
>>
>> causes Cygwin to ignore noacl in etc/fstab and create C:\foo with
>> POSIX-like permissions (non-NTFS default and not inherited from parent
>> directory C:\).
>>
>> According to http://cygwin.com/1.7/cygwin-ug-net.html#mount-table
>>
>> "Otherwise, the handling of MS-DOS filenames bypasses the mount table"
>>
>> But if Cygwin 1.7 bypasses etc/fstab for MS-DOS filenames and no longer
>> supports the nontsec option, I'm stuck.
>>
>> When using MS-DOS destination paths in Cygwin 1.7, is there any way to get
>> noacl functionality - i.e. where Cygwin creates objects with NTFS default
>> permissions inherited from their parent directory rather than POSIX-like
>> permissions?
>>
>> If not, are there any plans to add such functionality to Cygwin 1.7?


On 11:59, Corinna Vinschen wrote:
> Not yet.  I'm reluctant to add a setting just for DOS paths.  What we
> could do is to handle incoming DOS paths always in dumb Windows mode
> (noacl,posix=0).  Given that they are not POSIX paths anyway, there's
> probably not a lot of sense in treating them POSIXy.
>
>
> Corinna


Thanks so much for replying Corinna. I completely agree that always 
handling DOS paths with noacl,posix=0 makes sense and is a substantial 
improvement.

I'm amazed how quickly you implemented this change into v1.7.0-36! 
Thanks so much!

Would you like any help updating the Cygwin User's Guide to reflect this 
change? If so:

(1) Should I submit a diff -u against
http://cygwin.com/1.7/cygwin-ug-net.html?

(2) Should I send the diff to cygwin-patches AT cygwin DOT com?

Holiday Greetings,
Lawrence

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/