Files and paths · Lesson 9 of 36 · 7 minutes

Checksums

Use deterministic training hashes to verify file identity.

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
Hash README
Run sha256sum README.txt.
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 README.txt
```
Remember: A checksum detects changes only relative to a trusted expected digest.
2
Hash hostname
Run sha256sum /etc/hostname.
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 /etc/hostname
```
Remember: A checksum detects changes only relative to a trusted expected digest.
3
Read checksum notes
Run cat /home/learner/data/checksums.txt.
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 /home/learner/data/checksums.txt
```
Remember: Reading a source file should precede changing it; avoid printing real secrets.

Understand the pattern

Checksums help verify downloads, backups, and scripts.

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.
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.

Worked example and expected result

$ sha256sum README.txt

a76968d5df26cfd59ecd7d080f8283d65e91ec7366d233b4b98233877aa154c6  /home/learner/README.txt

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

$ sha256sum /etc/hostname

f2363df30f6c91aa58e72ecafed71bad400712a0503c677679a032c1884638a7  /etc/hostname

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

$ cat /home/learner/data/checksums.txt

README.txt  fake hash changes when content changes
scripts/deploy.sh  review before running

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 “Checksums”, which interpretation is safe?A checksum detects changes only relative to a trusted expected digest.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 sha256sum workflow from “Checksums” 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: Rename workflow 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