Shell scripting · Lesson 4 of 31 · 8 minutes

Basename in scripts

Use basename to report script inputs.

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 script basename
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.
2
Basename through xargs
Run printf scripts/deploy.sh | xargs basename.
Hint & worked example
Format data deliberately, including separators and final newlines. Practice constructing a supported command from input words.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
printf scripts/deploy.sh | xargs basename
```
Remember: A format string controls output; a newline is data, not an automatic guarantee. Whitespace splitting does not safely represent every possible filename.
3
Review script helpers
Run history.
Hint & worked example
Review commands entered during this session. History is a navigation aid, not evidence that a command succeeded.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
history
```
Remember: Completion in this release checks command outcomes, not history strings alone.

Understand the pattern

Junior operators build confidence by gathering evidence before changing systems.

basename: Remove directory components from a path string.
String manipulation does not verify that the target exists.
printf: Format data deliberately, including separators and final newlines.
A format string controls output; a newline is data, not an automatic guarantee.
xargs: Practice constructing a supported command from input words.
Whitespace splitting does not safely represent every possible filename.
history: Review commands entered during this session. History is a navigation aid, not evidence that a command succeeded.
Completion in this release checks command outcomes, not history strings alone.

Worked example and expected result

$ basename scripts/deploy.sh

deploy.sh

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

$ printf scripts/deploy.sh | xargs basename

deploy.sh

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

$ history

   1  basename scripts/deploy.sh
   2  printf scripts/deploy.sh | xargs basename

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 “Basename in scripts”, which interpretation is safe?A command appearing in history proves it completed successfully.A successful first check guarantees that every dependent service is healthy.A format string controls output; a newline is data, not an automatic guarantee.

Apply it elsewhere

Before adapting the printf workflow from “Basename in scripts” to another server, what should you do?Skip output inspection whenever the command is familiar.Confirm the current directory, target identity, permissions, and the installed command behavior first.Paste the training paths unchanged into production.

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Dirname in scripts 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