Bird
Raised Fist0
Bash Scriptingscripting~10 mins

Shebang line (#!/bin/bash) in Bash Scripting - Interactive Code Practice

Choose your learning style10 modes available
Practice - 5 Tasks
Answer the questions below
1fill in blank
easy

Complete the code to write the correct shebang line for a Bash script.

Bash Scripting
[1]
Drag options to blanks, or click blank then click option'
A#!/usr/bin/node
B#!/usr/bin/python
C#!/bin/sh
D#!/bin/bash
Attempts:
3 left
💡 Hint
Common Mistakes
Using a Python or Node.js shebang line in a Bash script.
Forgetting the '#!' at the start of the line.
2fill in blank
medium

Complete the code to start a Bash script with the correct shebang line.

Bash Scripting
[1]
echo "Hello, world!"
Drag options to blanks, or click blank then click option'
A#!/bin/bash
B#!/usr/bin/python3
C#!/usr/bin/perl
D#!/bin/sh
Attempts:
3 left
💡 Hint
Common Mistakes
Using '#!/bin/sh' which may not support all Bash features.
Using a Python or Perl shebang line by mistake.
3fill in blank
hard

Fix the error in the shebang line to correctly run the script with Bash.

Bash Scripting
[1]
echo "Script is running"
Drag options to blanks, or click blank then click option'
A#!bin/bash
B#!/bin/bash
C#!/bin/bash script
D#!/bin/bash/
Attempts:
3 left
💡 Hint
Common Mistakes
Adding a trailing slash after '/bin/bash'.
Omitting the leading slash in the path.
Adding extra words after the interpreter path.
4fill in blank
hard

Fill both blanks to write a Bash script that starts with the correct shebang and prints a message.

Bash Scripting
[1]
echo [2]
Drag options to blanks, or click blank then click option'
A#!/bin/bash
B"Hello, Bash!"
C"Hello, world!"
D#!/usr/bin/python3
Attempts:
3 left
💡 Hint
Common Mistakes
Using the wrong shebang line.
Forgetting to put the message in quotes.
5fill in blank
hard

Fill all three blanks to create a Bash script with the correct shebang, a variable assignment, and a print statement.

Bash Scripting
[1]
name=[2]
echo "Hello, [3]!"
Drag options to blanks, or click blank then click option'
A#!/bin/bash
B"Alice"
C$name
D#!/usr/bin/python3
Attempts:
3 left
💡 Hint
Common Mistakes
Using the wrong shebang line.
Not quoting the string value.
Not using $ to reference the variable in echo.

Practice

(1/5)
1. What is the main purpose of the shebang line #!/bin/bash in a script?
easy
A. It sets the script's file permissions to executable.
B. It comments out the first line of the script.
C. It tells the system to use the Bash shell to run the script.
D. It defines a variable named shebang.

Solution

  1. Step 1: Understand the shebang line role

    The shebang line starts with #! and specifies the interpreter for the script.
  2. Step 2: Identify the interpreter in the line

    /bin/bash means the script will run using the Bash shell.
  3. Final Answer:

    It tells the system to use the Bash shell to run the script. -> Option C
  4. Quick Check:

    Shebang = interpreter path [OK]
Hint: Shebang line always shows which shell runs the script [OK]
Common Mistakes:
  • Thinking it is a comment line
  • Confusing it with file permissions
  • Assuming it defines variables
2. Which of the following is the correct way to write a shebang line for a Bash script?
easy
A. !#/bin/bash
B. #!/bin/sh
C. #!/bash/bin
D. #!/bin/bash

Solution

  1. Step 1: Check the correct shebang syntax

    The shebang line must start with #! followed by the full path to the interpreter.
  2. Step 2: Verify the path for Bash

    The correct path for Bash is /bin/bash, so the line is #!/bin/bash.
  3. Final Answer:

    #!/bin/bash -> Option D
  4. Quick Check:

    Shebang = #! + interpreter path [OK]
Hint: Shebang always starts with #! followed by interpreter path [OK]
Common Mistakes:
  • Swapping the order of # and !
  • Using wrong interpreter path
  • Confusing /bin/sh with /bin/bash (different shells)
3. Given this script saved as test.sh with executable permission:
#!/bin/bash
echo "Hello, $USER!"

What will be the output when you run ./test.sh?
medium
A. Hello, $USER!
B. Hello, your_username!
C. Hello, root!
D. Syntax error

Solution

  1. Step 1: Understand the shebang effect

    The shebang #!/bin/bash runs the script with Bash, which expands variables like $USER.
  2. Step 2: Predict variable expansion

    $USER is replaced by the current user's username, so output is Hello, your_username!.
  3. Final Answer:

    Hello, your_username! -> Option B
  4. Quick Check:

    Variable expansion in Bash = username [OK]
Hint: Bash expands $USER to your username when run with shebang [OK]
Common Mistakes:
  • Thinking $USER prints literally
  • Assuming root user always runs script
  • Expecting syntax error from shebang
4. You wrote a script starting with this line:
#! /bin/bash

But when you run it, you get: bad interpreter: No such file or directory. What is the likely problem?
medium
A. There is a space between #! and /bin/bash.
B. The script file is not executable.
C. The /bin/bash path does not exist on the system.
D. The script has Windows line endings.

Solution

  1. Step 1: Check the shebang syntax

    The shebang must start exactly with #! with no space after it.
  2. Step 2: Identify the error cause

    A space after #! causes the system to look for an invalid interpreter path, causing the error.
  3. Final Answer:

    There is a space between #! and /bin/bash. -> Option A
  4. Quick Check:

    No space after #! in shebang [OK]
Hint: No spaces allowed between #! and interpreter path [OK]
Common Mistakes:
  • Ignoring spaces in shebang line
  • Assuming file permission error
  • Not checking interpreter path correctness
5. You want to write a script that runs with Bash but also works if run with sh script.sh (without executable permission). Which shebang line should you use to ensure it always runs with Bash when executed directly?
hard
A. #!/usr/bin/env bash
B. #!/bin/bash
C. #!/bin/sh
D. #!/usr/local/bin/bash

Solution

  1. Step 1: Understand shebang with env

    #!/usr/bin/env bash uses the env command to find Bash in the user's PATH, making it portable.
  2. Step 2: Compare with fixed paths

    /bin/bash may not exist on all systems, and /bin/sh is often not Bash. /usr/local/bin/bash is less common.
  3. Step 3: Ensure script runs with Bash when executed directly

    Using #!/usr/bin/env bash ensures the script runs with Bash regardless of its location.
  4. Final Answer:

    #!/usr/bin/env bash -> Option A
  5. Quick Check:

    Use env to find Bash for portability [OK]
Hint: Use #!/usr/bin/env bash for portable Bash scripts [OK]
Common Mistakes:
  • Using /bin/sh which may not be Bash
  • Assuming /bin/bash exists everywhere
  • Ignoring PATH differences on systems
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard