Re: git bash
- From
- Dirk Süsserott <newsletter@dirk.my1.cc>
- Date
- Jul 18, 2011, 18:51 UTC
- Message-ID
- <4E2480BD.9000403@dirk.my1.cc>
- In-Reply-To
- <alpine.DEB.1.00.1107150114240.2642@bonsai2>
Hi Johannes,
Am 15.07.2011 01:15 schrieb Johannes Schindelin:
Show 19 quoted lines
> Hi Dirk, > > On Fri, 17 Jun 2011, Dirk Süsserott wrote: > >> I noticed the following: When the ext. HD is attached/mounted *before* I >> start the bash, then it works. But if I have a running bash and then >> mount the drive, I cannot cd to it. "No such path" or sth. It seems, >> that bash builds a list of available drives only at startup. Might that >> be your problem? If so, then close all bashs and re-open them after >> mounting the devices. > > This behavior is discussed here: > > http://permalink.gmane.org/gmane.comp.version-control.git/141867 > > (look for "NO_FSTAB_THREAD") > > Ciao, > Johannes
thank you for the pointer. That's what I've observed. To be honest, I'm one of the lazy guys and didn't really understand the impact of setting NO_FSTAB_THREAD at first glance. As I understood, setting it means "mounting drives afterwards works, but slows things down" and not setting it means the opposite. Meanwhile I'm familiar with re-starting my git-bash in case (that's not too bad for me). I almost never run git commands from cmd.exe because cmd.exe is rubbish.
But, again, thanx for the help; now I know how to fine-tune the behaviour if I wish.
Cheers, Dirk