Book Image

Bash Quick Start Guide

By : Tom Ryder

Book Image

Bash Quick Start Guide

By: Tom Ryder

Overview of this book

Bash and shell script programming is central to using Linux, but it has many peculiar properties that are hard to understand and unfamiliar to many programmers, with a lot of misleading and even risky information online. Bash Quick Start Guide tackles these problems head on, and shows you the best practices of shell script programming. This book teaches effective shell script programming with Bash, and is ideal for people who may have used its command line but never really learned it in depth. This book will show you how even simple programming constructs in the shell can speed up and automate any kind of daily command-line work. For people who need to use the command line regularly in their daily work, this book provides practical advice for using the command-line shell beyond merely typing or copy-pasting commands into the shell. Readers will learn techniques suitable for automating processes and controlling processes, on both servers and workstations, whether for single command lines or long and complex scripts. The book even includes information on configuring your own shell environment to suit your workflow, and provides a running start for interpreting Bash scripts written by others.

Preface

Who this book is for

What this book covers

To get the most out of this book

Free Chapter

What is Bash?

What Bash is and is not

Checking Bash is running

Identifying the Bash version number

Upgrading Bash on macOS X

Understanding Bash features

Choosing when to apply Bash

Choosing when to avoid Bash

Getting help with Bash

Bash Command Structure

Bash Command Structure

Using Bash interactively

Interactive key bindings

Simple commands

Shell metacharacters

Running commands in sequence

Stopping a command list on error

Running a command in the background

Essential Commands

Essential Commands

Distinguishing command types

Essential Bash builtin commands

Essential system commands

Input, Output, and Redirection

Input, Output, and Redirection

Redirecting output

Redirecting errors

Redirecting input

Variables and Patterns

Variables and Patterns

Using variables

Loops and Conditionals

Loops and Conditionals

Using the if keyword

Switching with the case keyword

Looping over shell words with for

Using Bash's C-style for loops

Using while loops

Scripts, Functions, and Aliases

Scripts, Functions, and Aliases

Choosing between functions and scripts

Using functions in scripts

Best Practices

Quoting correctly

Handling filenames starting with dashes

Separating output and diagnostics

Keeping scripts brief and simple

Keeping scripts flexible

Respecting and applying the user's configuration

Allowing scripts to run without user input

Limiting the scope of shell state changes

Avoiding path anti-patterns

Avoiding Bash for untrusted user input

Documenting scripts

Using temporary files cleanly

Cleaning up after a script

Tools to check shell scripts for problems

Other Books You May Enjoy

Other Books You May Enjoy

Leave a review - let other readers know what you think

Customer Reviews

5 star

0

4 star

0

3 star

0

2 star

0

1 star

0

Distinguishing command types

The commands you can use in a Bash script fall into three major categories:

Shell builtin commands: Included in Bash itself. These commands don't correspond to executable program files on your system; they are implemented in the bash binary itself. Examples are echo, type, and source.
Runtime commands: Defined in the shell at runtime, and written in the Bash language. These can be aliases or functions. They don't have executable program files of their own on disk either, and are defined at runtime during a Bash session, often by reading startup files. Examples vary between systems and users.
System commands: Invoke executable program files on your filesystem. These are the only kinds of commands that can also be run outside of Bash. Examples are grep, ping, and rm.

The executable programs called by system commands may be written in any...