hard20 pts · first answer countslinuxshelltroubleshooting

Bad interpreter with a ^M

A script edited on Windows fails with "/bin/bash^M: bad interpreter: No such file or directory". What is wrong?

A.The file has CRLF line endings, so the shebang names "bash\r"B.Bash is not installed in /bin on this distributionC.The script lacks execute permission for its ownerD.The first line must be #!/usr/bin/env sh on Linux

Discussion 0

Join free to post in the discussion.

Bad interpreter with a ^M

Discussion 0

Related questions