Files and paths · Lesson 8 of 36 · 8 minutes

File differences

Compare two training config files before editing either one.

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
Compare configs
Run diff data/config-a.conf data/config-b.conf.
Hint & worked example
Compare two text files; a difference is a meaningful nonzero status, not necessarily an execution error.
Inspect the differences. diff exits 1 when files differ and 0 when they match.
```
diff data/config-a.conf data/config-b.conf
```
Remember: Status 1 means differences for diff; shell status must be interpreted in command context.
2
Read config A
Run cat data/config-a.conf.
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 data/config-a.conf
```
Remember: Reading a source file should precede changing it; avoid printing real secrets.
3
Read config B
Run cat data/config-b.conf.
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 data/config-b.conf
```
Remember: Reading a source file should precede changing it; avoid printing real secrets.

Understand the pattern

Diff review is central to safe administration.

diff: Compare two text files; a difference is a meaningful nonzero status, not necessarily an execution error.
Status 1 means differences for diff; shell status must be interpreted in command context.
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

$ diff data/config-a.conf data/config-b.conf

--- /home/learner/data/config-a.conf
+++ /home/learner/data/config-b.conf
-listen 443 ssl;
+listen 8443 ssl;

Exit status: 1. This nonzero result is an expected part of this exercise.

$ cat data/config-a.conf

server_name learn.clairos.ai;
listen 443 ssl;
root /srv/www;

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

$ cat data/config-b.conf

server_name learn.clairos.ai;
listen 8443 ssl;
root /srv/www;

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 “File differences”, which interpretation is safe?Reading a source file should precede changing it; avoid printing real secrets.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 cat workflow from “File differences” 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: Checksums 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