Text and logs · Lesson 38 of 38 · 8 minutes

Text evidence bridge

Checkpoint numbered logs, sorted comparisons, and bounded pipelines.

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
Build a bounded auth view
Run grep denied /var/log/auth.log | nl | head -n 3.
Hint & worked example
Select input lines that match a pattern; -i ignores case, -n adds line numbers, and -v inverts selection. Number input lines for a readable evidence reference. Show the beginning of an input; -n sets how many lines to include.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
grep denied /var/log/auth.log | nl | head -n 3
```
Remember: No matches is exit status 1, which is different from a malformed invocation. Line numbers depend on the exact file version and numbering mode. A small sample may omit the failure. Choose the time window you actually need.
2
Compare account sets
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.
3
Count the source log
Run wc -l /var/log/auth.log.
Hint & worked example
Count input. -l counts newline characters, -w counts whitespace-delimited words, and -c counts bytes.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
wc -l /var/log/auth.log
```
Remember: Text without a final newline may have fewer counted lines than visible rows.

Understand the pattern

Combining text tools into defensible evidence helps operators explain what they know before they change anything.

grep: Select input lines that match a pattern; -i ignores case, -n adds line numbers, and -v inverts selection.
No matches is exit status 1, which is different from a malformed invocation.
nl: Number input lines for a readable evidence reference.
Line numbers depend on the exact file version and numbering mode.
head: Show the beginning of an input; -n sets how many lines to include.
A small sample may omit the failure. Choose the time window you actually need.
comm: Compare sorted line sets and select unique or common columns.
Both inputs must be sorted under the same ordering rules.
wc: Count input. -l counts newline characters, -w counts whitespace-delimited words, and -c counts bytes.
Text without a final newline may have fewer counted lines than visible rows.

Worked example and expected result

$ grep denied /var/log/auth.log | nl | head -n 3

     1	May 26 08:18:33 clairos-learn sshd[118]: denied password for root
     2	May 26 08:21:44 clairos-learn sshd[141]: denied password for admin
     3

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.

$ wc -l /var/log/auth.log

3 /var/log/auth.log

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 “Text evidence bridge”, which interpretation is safe?Both inputs must be sorted under the same ordering rules.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 comm workflow from “Text evidence bridge” 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.

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

01Incident template numberingNumber a runbook template so collaborators can reference exact fields.Practice

GNU Coreutils manual · GNU Bash manual