X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Thu, 19 Aug 2010 09:40:20 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Postinstall for mintty fails when installing "just for me" Message-ID: <20100819074020.GL11340@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <0105D5C1E0353146B1B222348B0411A20945256668 AT NIHMLBX02 DOT nih DOT gov> <20100817084858 DOT GA16404 AT calimero DOT vinschen DOT de> <0105D5C1E0353146B1B222348B0411A2094525666F AT NIHMLBX02 DOT nih DOT gov> <20100818084323 DOT GN11340 AT calimero DOT vinschen DOT de> <0105D5C1E0353146B1B222348B0411A20946F38AF4 AT NIHMLBX02 DOT nih DOT gov> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <0105D5C1E0353146B1B222348B0411A20946F38AF4@NIHMLBX02.nih.gov> 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 Aug 18 20:31, Buchbinder, Barry (NIH/NIAID) [E] wrote: > Corinna Vinschen sent the following at Wednesday, August 18, 2010 4:43 AM > > > >That usually just means you don't have admin privs. > > For the archive: That is indeed the case. > > >Here's the actual problem: > > cygdrive prefix / system binary,noacl,posix=0,auto > > > >The cygdrive prefix is set to the mount option "noacl". So the > >output from getfacl or ls or stat for this directory shows just fake > >permissions based on the DOS R/O flag. > > > >You're not an admin, so you're not allowed to write to this directory, > >see the cacls output. However, since the cygdrive prefix is mounted > >with "noacl", Cygwin tools just don't know it. > > With "acl", I had been getting annoying error messages about copying > permissions with "cp -p" on some network drives, so I switched > everything to "noacl". I'll try switching back to "acl", testing for > error messages, and going to "noacl" only on drives that seem to have > problems. Oh, I didn't say you have to go back to "acl". I was just pointing out the fact. The fact that "noacl" is perfectly valid is something we package maintainers have to keep in mind when creating postinstall scripts. Same for case-sensitivity. *make mental note* 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