Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Date: Thu, 5 May 2005 12:49:00 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Cc: eggert AT CS DOT UCLA DOT EDU Subject: Re: mkdir -p and network drives Message-ID: <20050505164900.GG5374@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com 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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87acn9aavq.fsf@penguin.cs.ucla.edu> User-Agent: Mutt/1.5.8i On Thu, May 05, 2005 at 09:35:53AM -0700, Paul Eggert wrote: >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. Cygwin has had this (windows) limitation since 1997. I don't think anyone is in a hurry to fix it. It isn't trivial to do. The main thing that seems to be affected is "mkdir -p" so if we just have to keep a localized patch for mkdir sitting around it seems like that is our best option. cgf -- 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/