Lab Report: The Bash Shell

Lab Summary

Connected via PuTTY (as described in Lab 225). Declared a local shorthand macro targeting the tar compression engine. Encountered functional errors when attempting to execute scripts situated outside the shell's active working directory. Resolved these errors successfully by appending the scripts' structural parent directory to the $PATH variable.

Aliases

Mapped verbose text inputs, such as tar -cvzf, to short key phrases like backup to boost terminal efficiency and reduce syntax errors.

The PATH Variable

Troubleshot command invocation barriers by modifying the list of directories Linux probes when deploying unrecognized strings.

Step-by-Step Walkthrough

Detailed record of each task performed during the lab focusing on BASH customizations.

SSH Connection

Connected to the EC2 instance via PuTTY following the process described in Lab 225.

Create an Alias for Backup Operations

Confirmed location within the /home/ec2-user/ folder utilizing pwd.
Invoked the alias protocol: alias backup='tar -cvzf ' binding four options to one word.
Utilized the new shorthand macro to compile a GZIP compressed instance of the CompanyA hierarchy: backup backup_companyA.tar.gz CompanyA.
Observed that the shell successfully recognized backup, executing the underlying tar binary silently, compressing records like Sections.csv and Schedules.csv.
Confirmed artifact integrity via the ls command revealing backup_companyA.tar.gz.

Terminal displaying the successful execution of the custom backup alias — Terminal: Utilizing a freshly declared alias to pass arguments downstream toward actual binaries

Explore and Update the PATH Environment Variable

Navigated explicitly into /home/ec2-user/CompanyA/bin which houses the hello.sh test script.
Executed the file locally utilizing relative binding: ./hello.sh. The response triggered successfully as "hello ec2-user".
Reverted backward one directory level to the parent: cd .. and tested executing blindly via just hello.sh.
Revealed a deliberate command not found error because the file no longer existed in the local relative plane.
Revealed the active configuration parameters dictating execution domains: echo $PATH.
Modified the active variable to inject the missing bin folder securely: PATH=$PATH:/home/ec2-user/CompanyA/bin.
Reattempted hello.sh locally without absolute or relative ./ locators, attaining success now that BASH queried the newly registered PATH boundary.

Terminal displaying successful script execution after path modification — Terminal: Successfully executing a script globally after modifying the active environment PATH

Command Reference

System customization utilities utilized during the session.

cmd

`alias`

Instructs the shell to replace one string with another string whenever executing commands.

cmd

`echo $PATH`

Requests the shell to print the literal value of the PATH variable globally active in memory.

cmd

`PATH=$PATH:/new/path`

Syntax used to formally concatenate the preexisting arrays of the PATH environment alongside a new custom directory string.

Key Learnings

What Was Learned

✓

Creating shortcuts for elaborate operations that rely on rigid syntax parameters utilizing alias.

✓

Understanding why files situated outside the current execution path are rejected by native bash rendering.

✓

Overwriting environment variables (like $PATH) securely without corrupting existing values by utilizing standard self-referencing operations.

Technical Conclusion

Mastering the Bash shell elevates an operator from passively using Linux to actively configuring it. By appending highly utilized scripts securely into the $PATH variable, custom enterprise applications can mimic native OS behavior globally.

Aliasing remains pivotal for guaranteeing complex strings of code, such as those controlling backup compression, are not mistyped during emergencies or exhausted shifts.