Files and paths · Lesson 36 of 36 · 8 minutes

Files and paths bridge

Checkpoint file type, canonical path, inventory comparison, and integrity checks.

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
Identify the script
Run file scripts/deploy.sh.
Hint & worked example
Identify a file from its characteristics rather than trusting only the filename extension.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
file scripts/deploy.sh
```
Remember: The simulator uses a small reviewed type classifier, not the full system magic database.
2
Resolve the script path
Run realpath scripts/deploy.sh.
Hint & worked example
Resolve a path to its canonical location in the virtual filesystem.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
realpath scripts/deploy.sh
```
Remember: Resolving a path and reading its contents are separate operations.
3
Compare user inventories
Run comm data/users-a.txt data/users-b.txt.
Hint & worked example
Compare sorted line sets and select unique or common columns.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
comm data/users-a.txt data/users-b.txt
```
Remember: Both inputs must be sorted under the same ordering rules.
4
Hash the script
Run sha256sum scripts/deploy.sh.
Hint & worked example
Compare content digests to detect byte changes, not to establish who authored the file.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
sha256sum scripts/deploy.sh
```
Remember: A checksum detects changes only relative to a trusted expected digest.

Understand the pattern

Combining safe filesystem inspection habits helps operators explain what they know before they change anything.

file: Identify a file from its characteristics rather than trusting only the filename extension.
The simulator uses a small reviewed type classifier, not the full system magic database.
realpath: Resolve a path to its canonical location in the virtual filesystem.
Resolving a path and reading its contents are separate operations.
comm: Compare sorted line sets and select unique or common columns.
Both inputs must be sorted under the same ordering rules.
sha256sum: Compare content digests to detect byte changes, not to establish who authored the file.
A checksum detects changes only relative to a trusted expected digest.

Worked example and expected result

$ file scripts/deploy.sh

/home/learner/scripts/deploy.sh: POSIX shell script, ASCII text

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

$ realpath scripts/deploy.sh

/home/learner/scripts/deploy.sh

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

$ comm data/users-a.txt data/users-b.txt

admin
	backup
		learner
		www-data

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

$ sha256sum scripts/deploy.sh

f7d569c8d8504a5ddbe9ac442362c65f068aeacd1f540b24ca1ec84b7c27359e  /home/learner/scripts/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 “Files and paths bridge”, which interpretation is safe?A successful first check guarantees that every dependent service is healthy.Resolving a path and reading its contents are separate operations.A command appearing in history proves it completed successfully.

Apply it elsewhere

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

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Review this course 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

01Archive manifest workflowCreate an archive, list its members, and hash the artifact.Practice

GNU Coreutils manual · GNU Bash manual