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: Thu, 05 May 2005 14:00:21 -0400
From: "Pierre A. Humblet" <Pierre DOT Humblet AT ieee DOT org>
Subject: Re: mkdir -p and network drives
To: "Paul Eggert" <eggert AT CS DOT UCLA DOT EDU>, "Eric Blake" <ebb9 AT byu DOT net>
Cc: <cygwin AT cygwin DOT com>, <bug-coreutils AT gnu DOT org>
Reply-to: "Pierre A. Humblet" <Pierre DOT Humblet AT ieee DOT org>
Message-id: <05b301c5519c$51107bf0$3e0010ac@wirelessworld.airvananet.com>
MIME-version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7bit
References: <3 DOT 0 DOT 5 DOT 32 DOT 20050502232204 DOT 00b52180 AT incoming DOT verizon DOT net> <42777719 DOT 8090103 AT byu DOT net> <8764xym6vf DOT fsf AT penguin DOT cs DOT ucla DOT edu> <427A147D DOT 2030109 AT byu DOT net> <87acn9aavq DOT fsf AT penguin DOT cs DOT ucla DOT edu>


----- Original Message ----- 
From: "Paul Eggert" <eggert AT CS DOT UCLA DOT EDU>
To: "Eric Blake" <ebb9 AT byu DOT net>
Cc: "Pierre A. Humblet" <Pierre DOT Humblet AT ieee DOT org>; <cygwin AT cygwin DOT com>;
<bug-coreutils AT gnu DOT org>
Sent: Thursday, May 05, 2005 12:35 PM
Subject: Re: mkdir -p and network drives


> Eric Blake <ebb9 AT byu DOT net> writes:
>
> > //MACHINE currently generates ENOENT, whether or not there is a
> > server on the network with that name, and mkdir(2), stat(2), and
> > chdir(2) with an argument of "//MACHINE" fail.
>
> That's certainly a hassle.  Let's not worry about going through
> zillions of lines of application code working around that
> incompatibility.  Let's get Cygwin fixed instead.

The minimum required seems to be to have chdir(2) and stat(2) for
// and //MACHINE. Initially stat could report the permissions as x only.
That seems very easy if we don't check the existence of MACHINE.
(After all, any MACHINE could be there. Failures would occur only
when trying to access).
In a later phase the permissions could be rx, in which case readdir(2)
should
work and network scanning becomes necessary.

Pierre



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