Introduction to Bash Shell Scripting

Bash (Bourne Again SHell) is the default command-line interpreter for most Linux distributions. While executing individual commands in the terminal is useful, Bash Shell Scripting allows you to group these commands into a single file to automate repetitive tasks, manage system configurations, and handle complex workflows. For developers and system administrators, mastering Bash is essential for productivity and automation.

What is a Bash Script?

A Bash script is essentially a plain text file containing a series of commands that the shell executes in sequence. It follows a specific syntax and can include variables, loops, conditional logic, and functions. Think of it as a program written specifically for the Linux environment.

The Shebang (#!)

Every Bash script should start with a special line called the Shebang. This line tells the operating system which interpreter to use to execute the script. For Bash scripts, the standard shebang is:

#!/bin/bash

Creating and Running Your First Script

To create a script, follow these three basic steps:

• Create the file: Use a text editor like Nano or Vim to create a file with a .sh extension.
• Add the Shebang and Commands: Write your logic inside the file.
• Grant Execution Permissions: Use the chmod command to make the file executable.

Example: A Simple Automation Script

As a Java developer, you might want a script that cleans a directory, compiles a Java file, and runs the application. Here is how that looks in Bash:

#!/bin/bash

# Define a variable for the project name
PROJECT_NAME="HelloWorld"

echo "Starting build process for $PROJECT_NAME..."

# Remove old class files
rm -f *.class

# Compile the Java source code
javac $PROJECT_NAME.java

# Check if compilation was successful
if [ $? -eq 0 ]; then
    echo "Compilation successful. Running program..."
    java $PROJECT_NAME
else
    echo "Compilation failed."
fi

Working with Variables

Variables in Bash do not require data type declarations. However, it is important to remember that there should be no spaces around the equals sign during assignment.

• Correct: NAME="Linux"
• Incorrect: NAME = "Linux"

To access the value of a variable, use the dollar sign ($) prefix.

Common Mistakes to Avoid

• Incorrect Shebang: Using #!/bin/sh instead of #!/bin/bash can lead to errors if you use Bash-specific features, as sh is a more limited shell.
• Missing Permissions: Forgetting to run chmod +x script.sh will result in a "Permission denied" error.
• Windows Line Endings: If you write a script on Windows and move it to Linux, the hidden \r characters (CRLF) will break the script. Use dos2unix to fix this.
• Spacing in Conditionals: In Bash, the brackets in an if statement require spaces: if [ $VAL -eq 1 ] is correct, while if [$VAL -eq 1] will fail.

Real-World Use Cases

Bash scripting is widely used in the industry for various purposes:

• Log Rotation and Cleanup: Automatically deleting or compressing old log files to save disk space.
• CI/CD Pipelines: Automating the build, test, and deployment phases of a software project (e.g., Jenkins or GitHub Actions).
• System Monitoring: Writing scripts that check disk usage or CPU load and send alerts if thresholds are exceeded.
• Environment Setup: Standardizing the installation of Java, databases, and configuration files across multiple servers.

Interview Notes

• What is the difference between Shell and Bash? The Shell is an interface (a specification), while Bash is a specific implementation of a shell.
• How do you capture the output of a command into a variable? Use backticks or the $() syntax. For example: CURRENT_DIR=$(pwd).
• What does $? represent? It holds the exit status of the last executed command. 0 usually means success, while any non-zero value indicates an error.
• How do you pass arguments to a script? Use positional parameters like $1, $2, etc. $0 refers to the script name itself.

Summary

Bash shell scripting is a powerful tool for any Linux user. By combining simple commands with logic like variables and conditionals, you can automate complex tasks that would otherwise take hours to perform manually. Remember to always include the shebang, manage your file permissions, and test your scripts in a safe environment before deploying them to production servers.