bash v3.1.17(1)-release doesn't automatically recognize new drive letter

[stlee987]

The bash v3.1.17(1)-release in Gow 0.8.0 does not automatically recognize a portable drive plugged into the USB port. For example, when a drive is mapped on E:, I get the following:

$ cd e:/ bash.exe: cd: e:/: No such file or directory $ cd E:/ bash.exe: cd: E:/: No such file or directory $ cd /e bash.exe: cd: /e: No such file or directory

The workaround is to exit all bash windows and restart it. Then it recognizes the new drive letter but that's quite annoying. In the bash 2.03 version that I previously used from http://www.steve.org.uk/Software/bash/, it did not have this problem.

[stevebovy]

How do you get bash working?

When I type bash nothing changes and it looks like a NO-OP
and afterwards "exit" exits cmd.exe

[bytehead-]

IIRC, you need to create a ETC subdirectory under GOW to get it working. I think that get's fixed in the next release. But that doesn't help right now.