Getting User Input in a Shell Script

FAIL (the browser should render some flash content, not this).

Download in .ogv format

Comments

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

RE: echo $?

Chanan's picture

The $? variable is the exit status of the last command. $1 is the first command line argument passed to the script.

For example, make a script like the following (give it some name I used test.sh):

#!/bin/bash
echo $1
exit 23

Make it executable: chmod 755 test.sh
Then run it with an argument, for example: ./test.sh "Hello"
Then after that run: echo $?
You'll see that "echo $1" in the script returned the argument you passed, while "echo $?" returned the number after "exit" in the script (the exit status).

I used an exit status other then 0 (true) or 1 (false) to hopefully make the example clearer.

Oops, meant to put it as a

Chanan's picture

Oops, meant to put it as a reply to Arup's question.

echo $?

Arup's picture

Good tip Thanks,

but how does the ? in echo$? work
IS it like $1 ?

Zenity

Anonymous's picture

I also use Zenity for most of my shell scripts, being on gnome I guess thats my alternative to kdialog.

White Paper
Fabric-Based Computing Enables Optimized Hyperscale Data Centers

Today’s modular x86 servers are compute-centric, designed as a least common denominator to support a wide range of IT workloads. Those generic, virtualized IT workloads have much different resource optimization requirements than hyperscale and cloud applications. They have resulted in a “one size fits all” enterprise IT architecture that is not optimized for a specific set of IT workloads, and especially not emerging hyperscale workloads, such as web applications, big data, and object storage. In this report, you will learn how shifting the focus from traditional compute-centric IT architectures to an innovative disaggregated fabric-based architecture can optimize and scale your data center.

Learn More

Sponsored by AMD

White Paper
Red Hat White Paper: Using an Open Source Framework to Catch the Bad Guy

Built-in forensics, incident response, and security with Red Hat Enterprise Linux 6

Every security policy provides guidance and requirements for ensuring adequate protection of information and data, as well as high-level technical and administrative security requirements for a system in a given environment. Traditionally, providing security for a system focuses on the confidentiality of the information on it. However, protecting the data integrity and system and data availability is just as important. For example, when processing United States intelligence information, there are three attributes that require protection: confidentiality, integrity, and availability.

Learn more about catching the bad guy in this free white paper.

Learn More

Sponsored by DLT Solutions