Chris's Wiki :: blog/linux/BashNoInterpreterMsg Commentshttps://utcc.utoronto.ca/~cks/space/blog/linux/BashNoInterpreterMsg?atomcommentsDWiki2012-04-20T15:32:30ZRecent comments in Chris's Wiki :: blog/linux/BashNoInterpreterMsg.From 146.6.208.14 on /blog/linux/BashNoInterpreterMsgtag:CSpace:blog/linux/BashNoInterpreterMsg:8dae6fc0a1d930eb5f167aa8df6f22e070f5d62eFrom 146.6.208.14<div class="wikitext"><p>I've encountered errors like then when the script is on a filesystem which is mounted with the noexec option.</p>
</div>2012-04-20T15:32:30ZFrom 77.20.106.221 on /blog/linux/BashNoInterpreterMsgtag:CSpace:blog/linux/BashNoInterpreterMsg:aac140821e22040175df262fece9c1135f56afa2From 77.20.106.221<div class="wikitext"><p>I encountered this kind of problem several times, when someone edits his scripts on a windows machine. So the first line really reads "#!/bin/sh^M", and this interpreter of cause does not exists. The message usually prints the CR as well, so this differs from this problem description.</p>
</div>2012-04-20T07:03:03Z