# Use a text editor like vi or nano to create the text file called '''exitbreak-1.bash''' (eg. <span style="color:blue;font-weight:bold;font-family:courier;">vi exitbreak-1.bash</span>)<br><br># Enter the following lines in the '''exit.bash''' shell script:<br><span style="font-family:courier;font-weight:bold;">#!/bin/bash<br><br>if read -p "Enter a number: " number<br>while [ $# number -ne 1 5 ]<br>thendo<br> &nbsp; echo read -p "USAGETry again. Enter a number: $0 [arg]" &gt;&amp;2number<br>exit 1<br>fi<br><br>echo "The argument is: $1"</span><br><br>

# Issue the following command (without arguments):<br><span style="color:blue;font-weight:bold;font-family:courier;">./exit.bash</span><br><br>What did you notice?<br><br>Since there are no arguments, the test within the running shell script returns FALSE,<br>then an '''error message''' with feedback of how to properly issue the shell script with an argument<br>and then '''terminates''' the Bash shell script.<br><br>The symbol '''&gt;&amp;2''' redirects '''standard output''' from the USAGE message<br>to '''standard error''' making like a <u>real</u> error message.<br>This "''neat redirection trick''" will NOT be considered for evaluation for this coverage.<br><br>