X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS X-Spam-Check-By: sourceware.org Message-ID: <494C2CE4.1070105@cygwin.com> Date: Fri, 19 Dec 2008 18:23:16 -0500 From: "Larry Hall (Cygwin)" Reply-To: cygwin AT cygwin DOT com User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.18) Gecko/20081120 Remi/2.0.0.18-1.fc8.remi Lightning/0.9 Thunderbird/2.0.0.18 Mnenhy/0.7.5.0 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: noacl functionality for MS-DOS destination paths? References: <20081219114543 DOT GA24117 AT calimero DOT vinschen DOT de> <494C245F DOT 4060003 AT i12 DOT com> In-Reply-To: <494C245F.4060003@i12.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Note-from-DJ: This may be spam Lawrence Mayer wrote: >> 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? Actually, it would be The UG is a collection of SGML files that get cobbled together by other tools. > (2) Should I send the diff to cygwin-patches AT cygwin DOT com? 1 out of 2 ain't bad. ;-) Yes, that's the right place. Take a look at other patch submissions there to get an idea of what is needed. Thanks, -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _____________________________________________________________________ A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email? -- 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/