Very Computer

I'm attempting to install a linux program called pengaol (available at source
forge).  When I try to run the install script I get the following error (bash:
./Install: bad interpreter: No such file or directory).  I thought at first
that the problem wuz that for some reason it couldn't locate the file Install
however after reading a similar question I've learned that the problem could be
the first line of code in the file.  In this case it is !#/bin/sh.  If I type
ash on the command prompt it does switch to that shell but I do no for a fact
that there is no sh folder in bin.  Is this my problem?  If so how can I fix
it? If not what is my problem?  Please help me.  Send a responce to

[..]

Quote:> error (bash:
> ./Install: bad interpreter: No such file or directory).  I thought
> at first that the problem wuz that for some reason it couldn't
> locate the file Install however after reading a similar question
> I've learned that the problem could be
> the first line of code in the file.  In this case it is !#/bin/sh.

Really, it should be #!/bin/sh or #!/bin/bash.

Post here, read here.

Try:
$ echo $SHELL

put the output instead of #!/bin/sh, mostly #!/bin/bash, there is
no real sh on Linux,

Wonder how braindead the distro you are using is, or if it's a typo?

$ ls -al /bin/sh
lrwxrwxrwx    1 root     root      4 M?r 16  2001 /bin/sh -> bash

Just a symlink. (man ln)

Michael Heiming
--
Remove the +SIGNS case mail bounces.

| [..]
| > error (bash:
| > ./Install: bad interpreter: No such file or directory).  I thought
| > at first that the problem wuz that for some reason it couldn't
| > locate the file Install however after reading a similar question
| > I've learned that the problem could be
| > the first line of code in the file.  In this case it is !#/bin/sh.
|
| Really, it should be #!/bin/sh or #!/bin/bash.

Is it possible that you fetched this with FTP is ASCII mode, or got
it from a windows system somehow? Type this:

        sed 1q install | od -c

See if there's a trailing CR (^M, \015) char after the /bin/sh on that line.
This would indicate a DOS formatted text file. Which would indeed produce
this behaviour because they're trying to run "/bin/sh^M", not "/bin/sh".

Cheers,
--

Any profit should go to Arnie's `get the daemon carved on Mount Rushmore' fund.