How to Run a Script in Linux (bash and ./script.sh)

Run Bash and executable scripts correctly using an interpreter, execute permissions and a shebang.

Short answer

$ ./script.sh

If it is not executable, use `bash script.sh` or add execute permission with `chmod +x script.sh`.

Linux gives you two common ways to run a script: pass it to its interpreter, or execute it directly with a valid shebang and execute permission.

Step by step

$ bash script.sh

The file itself does not need execute permission when Bash reads it explicitly.

$ chmod +x script.sh

Adds execute permission without requiring world-write access.

$ ./script.sh

The ./ prefix explicitly names the file in the current directory. A valid shebang should identify the interpreter.

$ bash -x script.sh

Prints commands as Bash executes them.

Use `./script.sh`, not `script.sh`, unless its directory is intentionally on PATH.
Use LF line endings; CRLF can cause bad-interpreter errors.
Avoid chmod 777.

The current directory is normally not in PATH, so ./ explicitly names the local file.

No. Passing the file to Bash does not require the file itself to be executable.

The script may lack execute permission, a parent directory may block traversal, or the filesystem may use noexec.

The path resolves fine: the system simply will not let you do that with it.

Change file permissions with numeric (755, 644) and symbolic (u+x) modes: clearly explained.

List the contents of a directory, with options for hidden files, long format, sorting and more.

Print the first or last lines of a file, including live log following with tail -f.

Concepts involved: File permissions

See how much space is left, and find out what is using it.

Unpack tar.gz, tar.bz2, tar.xz and zip archives from the command line.

Find which process holds a port and stop it cleanly.

Replace text in one file or across a whole project, safely.