13,420
edits
Changes
→INVESTIGATION 2: SHE-BANG LINE / VARIABLES / PARAMETERS
# Issue the following to run your Bash shell script just by name:<br><span style="color:blue;font-weight:bold;font-family:courier;">hello.bash</span><br><br>Did your Bash shell script run?<br><br>
# Exit your Matrix session, and log back into your Matrix session.<br><br>
# Re-run the '''hello.bash''' shell script by just using the name.<br><br>What did you notice?<br><br>The setting of the '''PATH''' environment variable only worked in the current session only.<br>If you exit the current Matrix session, then the recently changed settings for environment variables will be lost.<br>You will in a <u>future</u> tutorial how to set environment variables in '''start-up''' files.<br><br><span style="color:red;">'''ATTENTION:''' Students will get FRUSTRATED when performing their '''assignment 3''' when their Bash shell scripts have errors. One major cause is the that the OUTPUT of their <u>your</u> Bash shell script when run does not NOT match the '''EXACTLY matchrequired output''' of the required output for the correct Bash shell scriptassignment checking program. This requires that you CAREFULLY '''read''' the requirements of your Bash shell script and create it to match the EXACT specifications</span>.<br><br>
# Issue the following Linux command to run a checking script:<br><span style="color:blue;font-weight:bold;font-family:courier;">bash /home/murray.saul/myscripts/week10-check-2 | more</span><br><br>If you encounter errors, make corrections and '''re-run''' the checking script until you<br>receive a congratulations message, then you can proceed.<br><br>Let's create a Bash shell script that contain '''user-created variables'''.<br><br>
# Use a text editor to create a Bash shell script called '''user-variables.bash'''<br><br>
