X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: References: Date: Wed, 1 Sep 2010 21:18:20 +0100 Message-ID: Subject: Re: Fwd: Windows File permissions are not being inherited - Cygwin 1.7 - Windows 7 From: Andy Koppe To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On 1 September 2010 15:18, Vasya Pupkin wrote: >> Do creating any entries in /etc/passwd =C2=A0or /etc/group or /etc/fstab >> files can overcome this... > > Nothing can overcome thins until setup.exe is modified to support > noacl option in /etc/fstab or get a similar comman line parameter or > even a checkbox. Reading /etc/fstab wouldn't work for the initial install. All these possibilities require a substantial amount of (voluntary) work, yet so far the only reason you've given for it was that you "don't like how cygwin works with NTFS permissions and therefore it is disabled through /etc/fstab". It shouldn't surprise you that that doesn't put it high on anyone's list of priorities. So why do you care about permissions on files that come with setup.exe packages? Setup.exe won't touch /home or anything outside the Cygwin install. Andy -- 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