Text and logs · Lesson 1 of 38 · 9 minutes

Viewing text

Open text, search logs, and inspect output without editing files.

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
Read the readme
Run cat README.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 README.txt
```
Remember: Reading a source file should precede changing it; avoid printing real secrets.
2
Tail the auth log
Run tail -n 3 /var/log/auth.log.
Hint & worked example
Show the end of an input; -n selects the number of lines.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
tail -n 3 /var/log/auth.log
```
Remember: This browser lab snapshots output; it does not keep a live tail -f stream.
3
Search denied logins
Run grep denied /var/log/auth.log.
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 denied /var/log/auth.log
```
Remember: No matches is exit status 1, which is different from a malformed invocation.

Understand the pattern

Most troubleshooting starts by reading evidence.

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.
tail: Show the end of an input; -n selects the number of lines.
This browser lab snapshots output; it does not keep a live tail -f stream.
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.

Worked example and expected result

$ cat README.txt

Welcome to Clairos Learn. This is a simulated filesystem for practicing terminal and server basics. Nothing here is connected to your real computer.

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

$ tail -n 3 /var/log/auth.log

May 26 08:18:33 clairos-learn sshd[118]: denied password for root
May 26 08:19:10 clairos-learn sudo[126]: learner : command=list services
May 26 08:21:44 clairos-learn sshd[141]: denied password for admin

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

$ grep denied /var/log/auth.log

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

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 “Viewing text”, which interpretation is safe?A successful first check guarantees that every dependent service is healthy.This browser lab snapshots output; it does not keep a live tail -f stream.A command appearing in history proves it completed successfully.

Apply it elsewhere

Before adapting the tail workflow from “Viewing text” 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.

Next: Grep practice 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