X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Wed, 24 Mar 2010 10:15:22 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Cygwin 1.7.1 breaks git on netapp shared drives Message-ID: <20100324091522.GS32321@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <608157 DOT 47595 DOT qm AT web110616 DOT mail DOT gq1 DOT yahoo DOT com> <747800 DOT 43893 DOT qm AT web110615 DOT mail DOT gq1 DOT yahoo DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <747800.43893.qm@web110615.mail.gq1.yahoo.com> User-Agent: Mutt/1.5.20 (2009-06-14) 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 Mar 23 16:37, Chris Idou wrote: > > > After a heck of lot of screwing around, I got this mount point stuff working. Now when I create files under cygwin they have the same permissions profile as they do when I create them under windows. > > BUT... > > git doesn't work still. It fails with the exact same error of "unable to set permission". How do the cygwin APIs work under noacl? They shouldn't ever return error code should they? They should. There's the one case in which you're trying something like chmod 444. Under noacl conditions this sets the DOS R/O attribute. If that fails, the call fails. 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