Message-ID: <438D12915E64D2118AB10000F8C1C0780143A426@zcard00e.ca.nortel.com> From: "Ian Chapman" To: "'Eli Zaretskii'" Cc: djgpp AT delorie DOT com Subject: RE: Bash sh Date: Wed, 19 Jan 2000 08:51:13 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01BF6284.41B40E2C" Reply-To: djgpp AT delorie DOT com This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01BF6284.41B40E2C Content-Type: text/plain; charset="iso-8859-1" -----Original Message----- From: Eli Zaretskii [mailto:eliz AT is DOT elta DOT co DOT il] Sent: Wednesday, January 19, 2000 5:21 AM To: Chapman, Ian [CAR:TM14:EXCH] Cc: djgpp AT delorie DOT com Subject: Re: Bash sh On Tue, 18 Jan 2000, Ian Chapman wrote: > First they do not seem to be executable. Please explain what do you mean by that. DOS/Windows filesystems don't have the execute bit in the file's attributes. DJGPP library functions consider a file executable if (among other possibilities) it has the telltale "#! /bin/sh" string on its first line. But even if there's no such line, I don't think the ported Bash would mind (although I didn't test that right now). What exactly happens when the scripts do NOT run? Error messages? Crashes? Please describe this. // command not found > However, they do run some of the time. I think if I look at them with > less after that the system seems to know what they are. This sounds like a black magic to me. How come viewing a file with Less suddenly changes how the filesystem treats it? // That's what I was asking myself. Maybe it was a typo but I did recheck as I was really puzzled. On what OS did you see this? // bash in a win95 dos window. Bash was invoked as the logon shell per info I received fro this news group some time back. > Second I thought that these were a > wee bit like .bat files once the header was set up all you needed on the > second etc. lines was:- > my_prog my_data > however, it can not find my_prog which is in ~/bin. Is "~/bin" in your PATH? // yes and ~/bin/sh // My 2nd question was should (My_prog My_data) on line 2 what exactly should I type get it to run. Maybe it's to do with exporting the environment path to a sub shell. Sorry if I'm confusing you. Maybe I should try bash as a shell running under dos. Regards Ian. ------_=_NextPart_001_01BF6284.41B40E2C Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: Bash sh

-----Original Message-----
From: Eli Zaretskii [mailto:eliz AT is DOT elta DOT co DOT il]=
Sent: Wednesday, January 19, 2000 5:21 AM
To: Chapman, Ian [CAR:TM14:EXCH]
Cc: djgpp AT delorie DOT com
Subject: Re: Bash sh



On Tue, 18 Jan 2000, Ian Chapman wrote:

> First they do not seem to be executable.

Please explain what do you mean by that.  = DOS/Windows filesystems don't
have the execute bit in the file's attributes.  = DJGPP library functions
consider a file executable if (among other = possibilities) it has the
telltale "#! /bin/sh" string on its first = line.  But even if there's no
such line, I don't think the ported Bash would mind = (although I didn't
test that right now).

What exactly happens when the scripts do NOT = run?  Error messages? 
Crashes?  Please describe this.
//  command not found

> However, they do run some of the time.  I = think if I look at them with
> less after that the system seems to know what = they are.

This sounds like a black magic to me.  How come = viewing a file with Less
suddenly changes how the filesystem treats = it?
//  That's what I was asking myself.  = Maybe it was a typo but I did recheck
as I was really puzzled.

On what OS did you see this?
// bash in a win95 dos window.  Bash was = invoked as the logon shell per info I received fro this news group some = time back.

> Second I thought that these were a
> wee bit like .bat files once the header was set = up all you needed on the
> second etc. lines was:-
> my_prog  my_data
>       =         however, it can not find = my_prog which is in ~/bin.

Is "~/bin" in your PATH?
//  yes and ~/bin/sh

//  My 2nd question was should (My_prog  = My_data) on line 2
what exactly should I type get it to run.  = Maybe it's to do with
exporting the environment path to a sub = shell.

        =         Sorry if I'm = confusing you.  Maybe I should try bash as a
shell running under dos.

        =         Regards = Ian.

------_=_NextPart_001_01BF6284.41B40E2C--