Permissions and users · Lesson 13 of 33 · 8 minutes

Executable scripts

Read and mark a training deploy script executable.

Open the lab Course map

Mastery 0/3Run itExplain itApply it

learner@clairos:~ $

↑ history · Tab complete · Ctrl+C cancel · Esc, Tab to leaveExit 0

Your objectives

Hints are always available. Wrong turns never cost XP.

1
Read deploy script
Run cat scripts/deploy.sh.
Hint & worked example
Read one or more files to standard output without editing their contents.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
cat scripts/deploy.sh
```
Remember: Reading a source file should precede changing it; avoid printing real secrets.
2
Make executable
Run chmod 755 scripts/deploy.sh.
Hint & worked example
Change permissions using an octal mode or a symbolic adjustment. Each rwx bit belongs to owner, group, or other.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
chmod 755 scripts/deploy.sh
```
Remember: Do not use 777 as a blanket fix. Grant the smallest access needed.
3
List script
Run ls -l scripts/deploy.sh.
Hint & worked example
List directory entries; -a includes hidden names and -l adds ownership and permission detail.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
ls -l scripts/deploy.sh
```
Remember: A listing is not proof that you can read or modify every listed file.

Understand the pattern

Executable scripts can change systems quickly in real life.

cat: Read one or more files to standard output without editing their contents.
Reading a source file should precede changing it; avoid printing real secrets.
chmod: Change permissions using an octal mode or a symbolic adjustment. Each rwx bit belongs to owner, group, or other.
Do not use 777 as a blanket fix. Grant the smallest access needed.
ls: List directory entries; -a includes hidden names and -l adds ownership and permission detail.
A listing is not proof that you can read or modify every listed file.

Worked example and expected result

$ cat scripts/deploy.sh

#!/bin/sh
set -eu
echo fake deploy: build static files
echo fake deploy: run nginx -t

Exit status: 0. The command completed successfully in the training fixture.

$ chmod 755 scripts/deploy.sh

(no output; exit 0)

Exit status: 0. The command completed successfully in the training fixture.

$ ls -l scripts/deploy.sh

--rwxr-xr-x learner learners    85 deploy.sh

Exit status: 0. The command completed successfully in the training fixture.

Try a variation

Repeat this workflow in the sandbox with a different scratch filename. Keep the system fixtures unchanged and compare the observed output with your expectation before moving on.

Explain it

In “Executable scripts”, which interpretation is safe?A command appearing in history proves it completed successfully.A successful first check guarantees that every dependent service is healthy.Do not use 777 as a blanket fix. Grant the smallest access needed.

Apply it elsewhere

Before adapting the chmod workflow from “Executable scripts” to another server, what should you do?Skip output inspection whenever the command is familiar.Confirm the current directory, target identity, permissions, and the installed command behavior first.Paste the training paths unchanged into production.

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Sensitive path audit Try an incident drill

Anonymous lesson and mastery progress lasts for this session. Sign in to keep synced lesson XP between sessions; mastery stays device-local. No speed bonus, lost lives, or hint penalties.

Keep learning

GNU Coreutils manual · GNU Bash manual