Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Thu, 05 May 2005 14:00:21 -0400 From: "Pierre A. Humblet" Subject: Re: mkdir -p and network drives To: "Paul Eggert" , "Eric Blake" Cc: , Reply-to: "Pierre A. Humblet" 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.0.5.32.20050502232204.00b52180@incoming.verizon.net> <42777719.8090103@byu.net> <8764xym6vf.fsf@penguin.cs.ucla.edu> <427A147D.2030109@byu.net> <87acn9aavq.fsf@penguin.cs.ucla.edu> ----- Original Message ----- From: "Paul Eggert" To: "Eric Blake" Cc: "Pierre A. Humblet" ; ; Sent: Thursday, May 05, 2005 12:35 PM Subject: Re: mkdir -p and network drives > Eric Blake 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/