Skip to contentSkip to conversation

git bash

DISCUSSION Massimo Manca 4 participants 6 messages Jun 15, 2016

lore
Share & tools
lore
#0 lore raw

Hi all,
I am using git on Linux Ubuntu, Windows Vista, , Windows 7 and Windows XP (several o.s. to develop sw).
In my notebook under Vista if I use bash on mi physical HD (it is divided in C:, F:, H:) it works, if I try to open a bash console on an external HD (or USB or SD memories) and also on network shared drives it doesn't work.
Have I configuration problems? I installed last msys git distribution and I choose to use bash shell also in Win to have the same commands on both linux and win.
Best regards,

begin:vcard
fn:Massimo Manca
n:Manca;Massimo
org:Micron Engineering di Massimo Manca adr:;;via della Ferriera, 48;Pordenone;PN;33170;ITALIA email;internet:[email protected] tel;work:+39 0434 1856131
tel;fax:+39 0434 1851032 / 178 273 3543 tel;cell:+39 349 4504979 url:http://www.micronengineering.it version:2.1
end:vcard

#1 lore raw
Quoted 5 lines · Massimo Manca

Hi all,
I am using git on Linux Ubuntu, Windows Vista, , Windows 7 and Windows XP (several o.s. to develop sw).
In my notebook under Vista if I use bash on mi physical HD (it is divided in C:, F:, H:) it works, if I try to open a bash console on an

Assuming you mean that git doesn't work (rather than bash), could you provide a transcript of what you think went wrong?

Quoted 2 lines

external HD (or USB or SD memories) and also on network shared drives it doesn't work.

Are these filsystems FAT32 by any chance. You may need to turn on a couple of compatibility options like case-insensitivity and filemode.

cmn

Signature · 3 lines
Carlos Martín Nieto | http://cmartin.tk

"¿Cómo voy a decir bobadas si soy mudo?" -- CACHAI
#2 lore raw

Am 17.06.2011 16:18 schrieb Carlos Martín Nieto:

Quoted 7 lines · Massimo Manca
Quoted 5 lines

Hi all,
I am using git on Linux Ubuntu, Windows Vista, , Windows 7 and Windows XP (several o.s. to develop sw).
In my notebook under Vista if I use bash on mi physical HD (it is divided in C:, F:, H:) it works, if I try to open a bash console on an

Quoted 8 lines

Assuming you mean that git doesn't work (rather than bash), could you provide a transcript of what you think went wrong?

Quoted 2 lines

external HD (or USB or SD memories) and also on network shared drives it doesn't work.

Are these filsystems FAT32 by any chance. You may need to turn on a couple of compatibility options like case-insensitivity and filemode.

But when using msysGit, these options are already set appropriate, aren't they?

Sometimes I have a similar problem. What do you mean by "opening a bash console on an external HD"? Do you right-click a folder and then "Git bash (here)"? I don't use that feature but I always start the bash with its regular icon (so my answer may probably not help you). It then starts in my $HOME and I change to the external HD (say X:) like so:

$ cd /x/foo

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.

HTH,
Dirk

#3 lore raw

Il 17/06/2011 16.39, Dirk Süsserott ha scritto:

Quoted 10 lines

Am 17.06.2011 16:18 schrieb Carlos Martín Nieto:

Quoted 9 lines · Massimo Manca
Quoted 5 lines

Hi all,
I am using git on Linux Ubuntu, Windows Vista, , Windows 7 and Windows XP (several o.s. to develop sw).
In my notebook under Vista if I use bash on mi physical HD (it is divided in C:, F:, H:) it works, if I try to open a bash console on an

Assuming you mean that git doesn't work (rather than bash), could you provide a transcript of what you think went wrong?

Quoted 6 lines
Quoted 4 lines
Quoted 2 lines

external HD (or USB or SD memories) and also on network shared drives it doesn't work.

Are these filsystems FAT32 by any chance. You may need to turn on a couple of compatibility options like case-insensitivity and filemode.

But when using msysGit, these options are already set appropriate, aren't they?

Yes they are.

Quoted 2 lines

Sometimes I have a similar problem. What do you mean by "opening a bash console on an external HD"?

Yes, it is more user friendly.

Quoted 6 lines

Do you right-click a folder and then "Git
bash (here)"? I don't use that feature but I always start the bash with its regular icon (so my answer may probably not help you). It then starts in my $HOME and I change to the external HD (say X:) like so:

$ cd /x/foo

Opening a bash shell from the icon and then changing the working folder.... it works :)
Very strange bug.

Quoted 7 lines

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.

In my situation the external HD (an SD card) it is always on.

Quoted 4 lines

HTH,
Dirk

begin:vcard
fn:Massimo Manca
n:Manca;Massimo
org:Micron Engineering di Massimo Manca adr:;;via della Ferriera, 48;Pordenone;PN;33170;ITALIA email;internet:[email protected] tel;work:+39 0434 1856131
tel;fax:+39 0434 1851032 / 178 273 3543 tel;cell:+39 349 4504979 url:http://www.micronengineering.it version:2.1
end:vcard

#4 lore raw
In reply to Dirk Süsserott

Hi Dirk,

Quoted 6 lines · Dirk Süsserott

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

#5 lore raw

Hi Johannes,

Am 15.07.2011 01:15 schrieb Johannes Schindelin:

Quoted 11 lines

Hi Dirk,

Quoted 6 lines · Dirk Süsserott

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.

Quoted 8 lines

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