Subject: Re: B19.1: bug using 'cd' in sh.exe
From: [email-masked] (Earnie Boyd)

27 Aug 1998 13:09:25 -0700
Message-ID: <[email-masked]>
Reply-To: [email-masked]
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
To: [email-masked], Eric Holter <[email-masked]>

---Eric Holter <[email-masked]> wrote:
>
> hello,
> i found that since bash.exe spawns sh.exe when one shell script calls
> another, baffeling behavior results when sh.exe behaves differently
from
> bash.exe.  in one case, i found that bash.exe can handle doing 'cd
> d:/src' but sh.exe cannot handle this syntax.  instead, you must do
'cd
> //d/src' or something similar.

mv sh.exe ash.exe
cp bash.exe sh.exe

> 
> futhermore, if you are currently in a directory like '//d/src', and
you
> try typing 'cd //d' from the bash.exe command prompt, you find that
you
> didn't really change directories at all after the 'cd' command.
> astoundingly, doing 'pwd' says '//d', but doing an 'ls' reveals that
you
> are actually still in '//d/src'.

Well, this is what MSDOS would do, isn't it?  Although, I do consider
it a bug in the filesystem emulation.

Work around:

Do one or both:

mount -b d:/ /d
mount -b d:/src /src

==
-        \\||//
---o0O0--Earnie--0O0o----
[email-masked]
------ooo0O--O0ooo-------

_________________________________________________________
DO YOU YAHOO!?
Get your free @yahoo.com address at http://mail.yahoo.com

-
For help on using this list (especially unsubscribing), send a message to
"[email-masked]" with one line of text: "help".