First, to improve jlliagre's answer, you may just use the hexa viewer, which is 'closer' to us programmers than octal viewer: $ head -1 yourscript hd -c You may then see: 00000000 ef bb bf 23 21 2f 62 69 6e 2f 62 61 73 68 0a .#! Download Slike Partizana Free Software. /bin/bash. 0000000 _ _ _ #! / b i n / b a s h n In which case you the BOM signature stands out: ef bb bf. Second, I can reproduce the exact error message seen by Nicolas by adding a BOM to the shell file. Thirdly, to comment on teknopaul: 'windows' is not at fault, it can happen on any OS. The responsible is the editor used.

I can't figure out where the shell is trying to run /usr/bin/virtualenvwrapper.sh. Sh: No such file or directory. Bin /usr/local/bin/ibm/lsf/9.1. Bash shell error: “no such file or directory. LCARS Desktop Theme For Win 7. Lazy.sh: No such file or directory. Lazy.sh with /usr/local/bin/virtualenvwrapper_lazy.sh and you. Requirement already satisfied (use --upgrade to upgrade): virtualenv in c:python27libsite-packages (from virtualenvwrapper).

An editor can add a BOM on Ubutu. Check your editor settings, not your OS's.

This usually happens when the shebang ( #! Jvc Everio Powerdirector Software. ) line in your script is broken. The shebang is what tells the kernel the file needs to be executed using an interpreter.

When run without sudo, the message is a little more meaningful. But with sudo you get the message you got. For example: $ cat test.sh #!/bin/foo echo bar $./test.sh bash:./test.sh: /bin/foo: bad interpreter: No such file or directory $ bash test.sh bar $ sudo./test.sh sudo: unable to execute./test.sh: No such file or directory $ sudo bash./test.sh bar The bad interpreter message clearly indicates that it's the shebang which is faulty.