From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 532 invoked by alias); 17 Jun 2011 09:53:44 -0000 Received: (qmail 502 invoked by uid 22791); 17 Jun 2011 09:53:25 -0000 X-Spam-Check-By: sourceware.org Received: from aquarius.hirmke.de (HELO calimero.vinschen.de) (217.91.18.234) by sourceware.org (qpsmtpd/0.83/v0.83-20-g38e4449) with ESMTP; Fri, 17 Jun 2011 09:53:09 +0000 Received: by calimero.vinschen.de (Postfix, from userid 500) id E69D52CADD2; Fri, 17 Jun 2011 11:53:06 +0200 (CEST) Date: Fri, 17 Jun 2011 09:53:00 -0000 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: Create file fails on network drives in cygwin-1.7.9-1 Message-ID: <20110617095306.GB5087@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20110616124954.GY12140@calimero.vinschen.de> <20110616145834.GA21703@calimero.vinschen.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2011-06/txt/msg00192.txt.bz2 On Jun 17 09:34, Pete Forman wrote: > On 16 June 2011 15:58, Corinna Vinschen wrote: > > Thanks.  AFAICS the permissions on that network drive don't allow a > > user to set the ACL of a file he or she's just creating.  In contrast > > to previous versions, Cygwin 1.7.9 requests the permission for that > > right at file creation time.  Unfortunately that fails due to the > > weird permission settings on that drive. > > > > Try to mount your drive with the noacl option to some arbitrary mount > > point, for instance: > > > >  mount -f -o noacl,binary X: /my_x_drive > > > > and then use the path below that mount point to access the drive. > > > > If that works, you can add the path to your personal fstab > > file (see http://cygwin.com/cygwin-ug-net/using.html#mount-table): > > > >  X: /my_x_drive none noacl,binary,posix=0 0 0 > > > > Please report back if it helped.  If so, I'll add some workaround for > > this problem to the next Cygwin version. > > My first couple of goes did not work reusing the /cygdrive mount > point. What did work was using /my_t as a mount point. Yes, that's what I wrote above. "and then use the path below that mount point to access the drive" > ## turn off acl > > $ mount -f -o noacl,binary H: /cygdrive/h That's not what I wrote above. You can't override the mode of a single cygdrive path. All cygdrive paths are subsumed under a single cygdrive mount entry. > ## switch off case sensitivity > > $ mount -f -o noacl,binary,posix=0 H: /cygdrive/h posix=0 is default for the cygdrive prefix anyway. That's also not what this issue is about. > $ mount -f -o noacl,binary T: /my_t Yes, that's what I wrote. > $ mount -f -o noacl,binary T: /cygdrive/t This, again, obviously can't work. > $ cd /my_t/Pete\ F > $ rm foo.txt > $ touch foo.txt Yes, that's what I expected. That's the workaround of choice. Btw., it would be an incredible good idea to change the permissions on the remote drive to allow users to set or change the permissions of files they created themselves. Otherwise you end up with non-POSIX permissions on the drive anyway, whether or not you're using "acl" or "noacl" mount option. If the network drives are not under your control, try to persuade the admin. If the admin is adamant, use the noacl mount option for these drives. You can also just change the cygdrive prefix to use noacl on all drives. See the User's Guide for how to do it. 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