From: jeffdbREMOVETHIS@goodnet.com (Mikey)
Subject: Re: Poor performance of bash cd command
21 Jul 1998 03:29:47 -0700
Message-ID: <35b56ab1.6454994.cygnus.gnu-win32@smtp.goodnet.com>
References: <35B2A551.90D9AE52@hp.com>
Reply-To: jeffdbREMOVETHIS@goodnet.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: earl@hpato.aus.hp.com, gnu-win32@cygnus.com

bash assumes : means remote host so you
1 load winsock
2 search for a host named c
3 discover no host
4 convert to cygwin32 path
5 cd /

the best thing to do is mount -b c:/ /c (if it isn't your root drive)
cd /c
see the list discussions (WARS) about text/binary for what the -b is for

a possible fix would be to change the search order in bash
so you attempt a local cd first, but this would probably break
many more things than it would fix

On Mon, 20 Jul 1998 12:02:57 +1000, you wrote:

>I'm running b19.1 with bash 2.01.1(2)-release.
>
>Why does:
>  cd e:/
>
>take about 10 seconds to execute (ensure that you're somewhere
>else first)?
>
>And:
>  cd //e
>
>takes the expected amount of time?
>
>Earl

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".