A script starts with #!/bin/bash but running ./script.sh gives bad interpreter: No such file or directory. What is the problem?

medium📝 Debug Q7 of 15

Bash Scripting - Basics

A script starts with #!/bin/bash but running ./script.sh gives bad interpreter: No such file or directory. What is the problem?

AThe path /bin/bash does not exist on the system

BThe script is missing execute permission

CThe script file is empty

DThe script has Windows line endings

Step-by-Step Solution

Solution:

Step 1: Understand bad interpreter error
This error often occurs if the shebang line has wrong line endings.
Step 2: Recognize Windows line endings cause this
Windows uses CRLF endings, which confuse Linux interpreters.
Final Answer:
The script has Windows line endings -> Option D
Quick Check:
Bad interpreter error often means wrong line endings [OK]

Quick Trick: Convert script to Unix line endings to fix bad interpreter error [OK]

Common Mistakes:

MISTAKES

Master "Basics" in Bash Scripting

9 interactive learning modes - each teaches the same concept differently

Want More Practice?

15+ quiz questions · All difficulty levels · Free

More Bash Scripting Quizzes