Capstone labs · Lesson 1 of 18 · 8 minutes

Capstone orientation

Start the final operator lab by mapping host, identity, and filesystem.

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
Check location
Run pwd.
Hint & worked example
Print the directory that relative paths currently resolve from.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
pwd
```
Remember: A relative path is interpreted from the working directory, not necessarily the home folder.
2
Check host
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
Check identity
Run id.
Hint & worked example
Inspect user identity and group membership.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
id
```
Remember: A file group is useful only when the acting user belongs to it or has an applicable override.
4
List root
Run ls /.
Hint & worked example
List directory entries; -a includes hidden names and -l adds ownership and permission detail.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
ls /
```
Remember: A listing is not proof that you can read or modify every listed file.

Understand the pattern

Junior operators build confidence by gathering evidence before changing systems.

pwd: Print the directory that relative paths currently resolve from.
A relative path is interpreted from the working directory, not necessarily the home folder.
hostname: Read the simulated host name.
A name helps orient an operator but is not proof of network reachability.
id: Inspect user identity and group membership.
A file group is useful only when the acting user belongs to it or has an applicable override.
ls: List directory entries; -a includes hidden names and -l adds ownership and permission detail.
A listing is not proof that you can read or modify every listed file.

Worked example and expected result

$ pwd

/home/learner

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.

$ id

uid=1000(learner) gid=1000(learners) groups=1000(learners),27(sudo-readonly)

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

$ ls /

bin  etc  home  Library  srv  tmp  var

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 “Capstone orientation”, which interpretation is safe?A successful first check guarantees that every dependent service is healthy.A name helps orient an operator but is not proof of network reachability.A command appearing in history proves it completed successfully.

Apply it elsewhere

Before adapting the hostname workflow from “Capstone orientation” 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: Capstone log sweep 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