Files and paths · Lesson 13 of 36 · 8 minutes

Script metadata

Inspect and update simulated script permissions.

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
Inspect deploy script
Run stat scripts/deploy.sh.
Hint & worked example
Inspect a file or directory metadata record, including ownership, permissions, and size.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
stat scripts/deploy.sh
```
Remember: Metadata and file contents answer different questions.
2
Set executable mode
Run chmod 700 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 700 scripts/deploy.sh
```
Remember: Do not use 777 as a blanket fix. Grant the smallest access needed.
3
Inspect again
Run stat scripts/deploy.sh.
Hint & worked example
Inspect a file or directory metadata record, including ownership, permissions, and size.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
stat scripts/deploy.sh
```
Remember: Metadata and file contents answer different questions.

Understand the pattern

Executable files deserve extra scrutiny.

stat: Inspect a file or directory metadata record, including ownership, permissions, and size.
Metadata and file contents answer different questions.
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.

Worked example and expected result

$ stat scripts/deploy.sh

Path: /home/learner/scripts/deploy.sh
Type: file
Mode: -rw-r--r--
Owner: learner
Group: learners
Size: 85 bytes

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

$ chmod 700 scripts/deploy.sh

(no output; exit 0)

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

$ stat scripts/deploy.sh

Path: /home/learner/scripts/deploy.sh
Type: file
Mode: -rwx------
Owner: learner
Group: learners
Size: 85 bytes

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 “Script metadata”, which interpretation is safe?Do not use 777 as a blanket fix. Grant the smallest access needed.A command appearing in history proves it completed successfully.A successful first check guarantees that every dependent service is healthy.

Apply it elsewhere

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

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: SSH file layout 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