Actually, Andy's right, the path to the interpreter is incorrect. But it's incorrect because the file has DOS-style CR-LF line endings. This makes the path to the shell seem to be: /bin/bash<0x0D> , which of course is a file that doesn't exist.On 10/18/05, Andy Pieters <mailings@xxxxxxxxxxxxxxxx> wrote:Hi: bad interpreter: No such file or directory $ PaulYou have to edit the very first line of that file and replace the #!/bin/bash with the path to your bash binary, after that it will work. But in light of recent discovery, a rewrite imposes itself to skip kmix and rely purly on amixer.Thanks, Andy. Paul
The error message that is (trying to be) printed is really: /bin/bash<0x0D>: bad interpreter: No such file or directory
But when it prints the <0x0D> character to the console, the cursor returns to the beginning of the line, leaving only the part starting with the colon left-justified on the screen.
Use the dos2unix utility to fix the script file. -- Fritz Whittington -- TI Alum -- http://www.tialumni.org "He not busy being born is busy dying." --Bob Dylan
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
