Terminal basics · Lesson 8 of 34 · 6 minutes

System identity

Inspect simulated kernel, hostname, and clock output.

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 kernel label
Run uname -a.
Hint & worked example
Inspect simulated operating-system identity.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
uname -a
```
Remember: A kernel string is not a complete inventory of packages or configuration.
2
Read hostname
Run hostname.
Hint & worked example
Read the simulated host name.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
hostname
```
Remember: A name helps orient an operator but is not proof of network reachability.
3
Read clock
Run date.
Hint & worked example
Read the lab clock representation and practice unambiguous timestamp labeling.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
date
```
Remember: Name the timezone when comparing evidence from different systems.

Understand the pattern

Identity checks prevent cross-server mistakes.

uname: Inspect simulated operating-system identity.
A kernel string is not a complete inventory of packages or configuration.
hostname: Read the simulated host name.
A name helps orient an operator but is not proof of network reachability.
date: Read the lab clock representation and practice unambiguous timestamp labeling.
Name the timezone when comparing evidence from different systems.

Worked example and expected result

$ uname -a

ClairosLearn 6.8.0-simulated #1 SMP Browser x86_64 GNU/Linux

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

$ hostname

clairos-learn-lab

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

$ date

Wed May 27 10:26:04 CDT 2026

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 “System identity”, which interpretation is safe?A name helps orient an operator but is not proof of network reachability.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 hostname workflow from “System identity” 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: Identity context 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