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 13:19:51 -0400 (EDT) From: Igor Pechtchanski Reply-To: cygwin AT cygwin DOT com To: Paul Eggert cc: Eric Blake , cygwin AT cygwin DOT com, bug-coreutils AT gnu DOT org Subject: Re: mkdir -p and network drives In-Reply-To: <87acn9aavq.fsf@penguin.cs.ucla.edu> Message-ID: 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 On Thu, 5 May 2005, 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. One potential problem is that on Windows, using NetShareEnum when checking the path will mean that every time someone does "mkdir -p", the command will have to wait until all network shares are examined. This could result in quite a bit of a delay, to say the least... Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu ZZZzz /,`.-'`' -. ;-;;,_ igor AT watson DOT ibm DOT com |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! "The Sun will pass between the Earth and the Moon tonight for a total Lunar eclipse..." -- WCBS Radio Newsbrief, Oct 27 2004, 12:01 pm EDT -- 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/