Keep public learning moving

Support the next lesson.

Optional one-time contributions support public learning tools, infrastructure, and new educational work. No account is required, and contributions are not tax deductible.

Contribute to Clairos

Save progress

Keep learning across sessions.

Create a free account to sync completed lessons, XP, streaks, course status, and your next lesson across sessions.

Checking account status...

Progress sync is idle.

0XP New learnerrank 0day streak 0best streak 0daily streak 0lessons 0courses 0missions 0tasks Noverified

Continue

Progress sync stores completion IDs, scores, streaks, badges, and game settings. Terminal contents, editor snippets, lab scratch, email, and real names are never published on leaderboards or share cards.

New account

Create a Learn account

Create your account, sign in immediately, and merge this browser's progress. We will also email optional verification and password setup links.

Email Name Email me Clairos Learn course updates.

Sign in and sync progress

Completed lessons, tasks, missions, and XP will merge with this browser.

Email Password

Password

Reset your password

If the email has a Learn account, a reset link will be sent.

Learn Updates

Get Learn updates

Course update emails require confirmation from your inbox.

Email Email me course updates.

Lesson support

What to notice while you play.

Objective

Create an incident timeline note.

Hint

Read the SSH journal after saving your timeline.

Why it matters

Incident reviews depend on ordered events.

Common mistakes

Writing vague notes.
Skipping the source log after writing the timeline.

Reference

Commands in this lesson.

nano <file>

Open a simulated nano editor.

cat <file>

Print text file contents.

journalctl -u <service>

Read simulated service journal entries.