Text and logs · Lesson 15 of 38 · 7 minutes

Redaction notes

Write a safe note that marks sensitive data as redacted.

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
Write redacted note
Run echo token=redacted > lab-redaction.txt.
Hint & worked example
Write simple text to standard output. Prefer printf when exact formatting matters.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
echo token=redacted > lab-redaction.txt
```
Remember: Redirection can overwrite an existing file before the command runs.
2
Search redacted
Run grep redacted lab-redaction.txt.
Hint & worked example
Select input lines that match a pattern; -i ignores case, -n adds line numbers, and -v inverts selection.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
grep redacted lab-redaction.txt
```
Remember: No matches is exit status 1, which is different from a malformed invocation.
3
Read redacted note
Run cat lab-redaction.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 lab-redaction.txt
```
Remember: Reading a source file should precede changing it; avoid printing real secrets.

Understand the pattern

Good notes preserve facts without spreading secrets.

echo: Write simple text to standard output. Prefer printf when exact formatting matters.
Redirection can overwrite an existing file before the command runs.
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.
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

$ echo token=redacted > lab-redaction.txt

(no output; exit 0)

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

$ grep redacted lab-redaction.txt

token=redacted

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

$ cat lab-redaction.txt

token=redacted

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 “Redaction notes”, which interpretation is safe?No matches is exit status 1, which is different from a malformed invocation.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 grep workflow from “Redaction notes” 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: Sed substitution 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