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: Sat, 7 May 2005 11:43:32 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: mkdir -p and network drives Message-ID: <20050507154332.GF11243@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com References: <87k6mc1au3 DOT fsf AT penguin DOT cs DOT ucla DOT edu> <20050506204324 DOT GJ29240 AT trixie DOT casa DOT cgf DOT cx> <8764xvbl2n 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: <8764xvbl2n.fsf@penguin.cs.ucla.edu> User-Agent: Mutt/1.5.8i On Fri, May 06, 2005 at 11:34:56PM -0700, Paul Eggert wrote: >Christopher Faylor writes: >>Except that it can't be made to work correctly due to a bash bug. > >Which Bash bug is that? Eric Blake alluded to it here: http://sources.redhat.com/ml/cygwin/2005-05/msg00254.html Bash is the most important program for which 'that chdir("//") is currently no different from chdir("/")'. >Bash bugs can be fixed. Our track record for getting cygwin fixes into bash has been mixed. I believe that someone has tried to get this fixed previously, along with an even more serious problem with bash getting confused by quick pid reuse but I believe that both problem still exist in bash 3.0. 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/