Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Wed, 12 Oct 2005 09:47:55 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: please test: coreutils-5.90-2
Message-ID: <20051012074755.GU12938@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <433F5562 DOT 1060806 AT byu DOT net> <loom DOT 20051009T042005-680 AT post DOT gmane DOT org> <434C3906 DOT 6090304 AT acm DOT org> <434C8100 DOT 9010503 AT byu DOT net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <434C8100.9010503@byu.net>
User-Agent: Mutt/1.4.2i

On Oct 11 21:20, Eric Blake wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> According to David Rothenberger on 10/11/2005 4:13 PM:
> > I'm having another problem with 'mkdir -p' in 5.90-2.
> > 
> > I have a script that attempts to do "mkdir -p c:/dir1/dir2/dir3". This
> > started failing with a permission denied error for c:/.
> 
> Hmm.  It worked perfectly for me on Win98, on both local and remote
> drives.  But on WinXP, I got different behavior for the remote FAT than I
> did for the local NTFS:
> 
> $ df -T c: j:
> Filesystem    Type   1K-blocks      Used Available Use% Mounted on
> c:    system,fixed    29286460  20471796   8814664  70% /cygdrive/c
> j:   system,remote     6260992   4508800   1752192  73% /cygdrive/j
> $ mkdir -p j:/dir
> $ mkdir -p c:/dir
> mkdir: cannot create directory `c:': Permission denied
> 
> I am suspecting a cygwin bug here.  mkdir("c:") should fail with EEXIST,
> not EACCES.  5.90 exposes this bug, where 5.3.0 did not, because the
> algorithm for mkdir -p was changed to attempt mkdir() first instead of stat().
> 
> Continuing the example, I also find it odd that from WinXP, I get EBADRQC
> instead of the more familiar ENOENT when removing a nonexistant directory
> on a remote FAT drive:

The error codes returned from a remote FAT filesystem on a 9x based
host are for some reason entirely different than the error codes you'd
expect from other experiences.

In both of the above cases, it would be helpful to run mkdir under
strace and search for the Win32 error number, usually in a line with
`geterrno_from_win_error' in it.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat, Inc.

--
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/