On 28-Nov-06 cl@isbd.net wrote:
On Tue, Nov 28, 2006 at 11:44:26AM +0000, Jenny Hopkins wrote:
Hullo there,
I've been setting up a debian box to be a clone of several other like boxen. The new box has amd64 architecture and the old i386. Apart from that they are all still on debian sarge, 2.6 kernels.
One thing all the boxen have in common is that they share files over an nfs mount from a server. Some of the files are binary executables.
Now, on the new box, they simply won't run: I get the error
balloon@capirossi:~$ /home/balloon/bin/balloon-audio-off bash: /home/balloon/bin/balloon-audio-off: No such file or directory
The same error appears when running it as root.
The file is executable. The selfsame file also runs no problem from the other computers using it. All I know about the file is that it invokes the bash shell and that it is sending data to the parallel port.
I put together a test bash script to idiot check bash and that ran ok.
It sounds as if the #! at the beginning of the script is pointing at the wrong location for bash (or at least a wrong location for something).
Look at the first line of /home/balloon/bin/balloon-audio-off and see if what it points at exists (and is executable) on the system where it fails to run.
That's a possible source of the problem. However, messages like
bash: /some/program: No such file or directory
can arise whenever something within /some/program fails to find a file or directory it is looking for, and what that "something" is may not be obvious.
The only sure way to track down this kind of thing is to work explicitly through the script, and observe which part of it is going wrong!
Good luck, Jenny! Ted.
-------------------------------------------------------------------- E-Mail: (Ted Harding) Ted.Harding@nessie.mcc.ac.uk Fax-to-email: +44 (0)870 094 0861 Date: 28-Nov-06 Time: 12:00:00 ------------------------------ XFMail ------------------------------