Terminal basics · Lesson 7 of 34 · 7 minutes

Environment variables

Inspect a simulated environment without exposing real browser or server secrets.

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
Print lab environment
Run env.
Hint & worked example
Inspect shell environment variables. Assignments and export affect the training environment, never your host shell.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
env
```
Remember: Environment output may expose real credentials outside the simulator.
2
Print a safe marker
Run echo PATH is fake.
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 PATH is fake
```
Remember: Redirection can overwrite an existing file before the command runs.
3
Confirm 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.

Understand the pattern

Many CLI tools read configuration from the environment.

env: Inspect shell environment variables. Assignments and export affect the training environment, never your host shell.
Environment output may expose real credentials outside the simulator.
echo: Write simple text to standard output. Prefer printf when exact formatting matters.
Redirection can overwrite an existing file before the command runs.
pwd: Print the directory that relative paths currently resolve from.
A relative path is interpreted from the working directory, not necessarily the home folder.

Worked example and expected result

$ env

HOME=/home/learner
USER=learner
SHELL=/bin/bash
PATH=/usr/local/bin:/usr/bin:/bin
PWD=/home/learner

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

$ echo PATH is fake

PATH is fake

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

$ pwd

/home/learner

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 “Environment variables”, which interpretation is safe?A successful first check guarantees that every dependent service is healthy.Redirection can overwrite an existing file before the command runs.A command appearing in history proves it completed successfully.

Apply it elsewhere

Before adapting the echo workflow from “Environment variables” 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: System identity 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