Shell scripting · Lesson 29 of 31 · 8 minutes

Script path resolution

Resolve script paths and report their directory and basename.

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
Resolve the script path
Run realpath scripts/deploy.sh.
Hint & worked example
Resolve a path to its canonical location in the virtual filesystem.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
realpath scripts/deploy.sh
```
Remember: Resolving a path and reading its contents are separate operations.
2
Print the script name
Run basename scripts/deploy.sh.
Hint & worked example
Remove directory components from a path string.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
basename scripts/deploy.sh
```
Remember: String manipulation does not verify that the target exists.
3
Print the script directory
Run dirname scripts/deploy.sh.
Hint & worked example
Extract the directory portion of a path string.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
dirname scripts/deploy.sh
```
Remember: A path can be syntactically valid without naming an existing directory.

Understand the pattern

Handling script paths without depending on the current directory helps operators explain what they know before they change anything.

realpath: Resolve a path to its canonical location in the virtual filesystem.
Resolving a path and reading its contents are separate operations.
basename: Remove directory components from a path string.
String manipulation does not verify that the target exists.
dirname: Extract the directory portion of a path string.
A path can be syntactically valid without naming an existing directory.

Worked example and expected result

$ realpath scripts/deploy.sh

/home/learner/scripts/deploy.sh

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

$ basename scripts/deploy.sh

deploy.sh

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

$ dirname scripts/deploy.sh

/scripts

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 “Script path resolution”, which interpretation is safe?A successful first check guarantees that every dependent service is healthy.String manipulation does not verify that the target exists.A command appearing in history proves it completed successfully.

Apply it elsewhere

Before adapting the basename workflow from “Script path resolution” 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: Script change review 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