2013-08-18 02:59:35 +04:00
|
|
|
---
|
2013-08-19 20:14:02 +04:00
|
|
|
category: tool
|
|
|
|
tool: bash
|
2013-08-18 02:59:35 +04:00
|
|
|
contributors:
|
2013-08-19 20:14:02 +04:00
|
|
|
- ["Max Yankov", "https://github.com/golergka"]
|
|
|
|
- ["Darren Lin", "https://github.com/CogBear"]
|
2013-09-22 08:06:35 +04:00
|
|
|
- ["Alexandre Medeiros", "http://alemedeiros.sdf.org"]
|
2013-12-18 12:37:27 +04:00
|
|
|
- ["Denis Arh", "https://github.com/darh"]
|
2014-07-23 10:43:18 +04:00
|
|
|
- ["akirahirose", "https://twitter.com/akirahirose"]
|
2014-08-06 22:30:15 +04:00
|
|
|
- ["Anton Strömkvist", "http://lutic.org/"]
|
2014-09-06 05:51:48 +04:00
|
|
|
- ["Rahil Momin", "https://github.com/iamrahil"]
|
2014-09-27 23:04:25 +04:00
|
|
|
- ["Gregrory Kielian", "https://github.com/gskielian"]
|
2015-04-26 20:22:48 +03:00
|
|
|
- ["Etan Reisner", "https://github.com/deryni"]
|
2013-08-18 02:59:35 +04:00
|
|
|
filename: LearnBash.sh
|
|
|
|
---
|
|
|
|
|
|
|
|
Bash is a name of the unix shell, which was also distributed as the shell for the GNU operating system and as default shell on Linux and Mac OS X.
|
|
|
|
Nearly all examples below can be a part of a shell script or executed directly in the shell.
|
|
|
|
|
|
|
|
[Read more here.](http://www.gnu.org/software/bash/manual/bashref.html)
|
|
|
|
|
|
|
|
```bash
|
2014-02-13 00:02:29 +04:00
|
|
|
#!/bin/bash
|
2013-08-19 20:14:02 +04:00
|
|
|
# First line of the script is shebang which tells the system how to execute
|
|
|
|
# the script: http://en.wikipedia.org/wiki/Shebang_(Unix)
|
2013-08-18 02:59:35 +04:00
|
|
|
# As you already figured, comments start with #. Shebang is also a comment.
|
|
|
|
|
|
|
|
# Simple hello world example:
|
2013-12-27 19:21:24 +04:00
|
|
|
echo Hello world!
|
2013-08-18 02:59:35 +04:00
|
|
|
|
|
|
|
# Each command starts on a new line, or after semicolon:
|
|
|
|
echo 'This is the first line'; echo 'This is the second line'
|
|
|
|
|
|
|
|
# Declaring a variable looks like this:
|
2015-04-30 05:11:20 +03:00
|
|
|
Variable="Some string"
|
2013-08-18 02:59:35 +04:00
|
|
|
|
|
|
|
# But not like this:
|
2015-04-30 05:11:20 +03:00
|
|
|
Variable = "Some string"
|
|
|
|
# Bash will decide that Variable is a command it must execute and give an error
|
2015-04-26 20:32:41 +03:00
|
|
|
# because it can't be found.
|
|
|
|
|
|
|
|
# Or like this:
|
2015-04-30 05:11:20 +03:00
|
|
|
Variable= 'Some string'
|
2015-04-26 20:32:41 +03:00
|
|
|
# Bash will decide that 'Some string' is a command it must execute and give an
|
2015-04-30 05:11:20 +03:00
|
|
|
# error because it can't be found. (In this case the 'Variable=' part is seen
|
2015-04-26 20:32:41 +03:00
|
|
|
# as a variable assignment valid only for the scope of the 'Some string'
|
|
|
|
# command.)
|
2013-08-18 02:59:35 +04:00
|
|
|
|
|
|
|
# Using the variable:
|
2015-04-30 05:11:20 +03:00
|
|
|
echo $Variable
|
|
|
|
echo "$Variable"
|
|
|
|
echo '$Variable'
|
2013-08-19 20:14:02 +04:00
|
|
|
# When you use the variable itself — assign it, export it, or else — you write
|
2015-10-02 17:08:27 +03:00
|
|
|
# its name without $. If you want to use the variable's value, you should use $.
|
2013-09-22 08:29:05 +04:00
|
|
|
# Note that ' (single quote) won't expand the variables!
|
|
|
|
|
|
|
|
# String substitution in variables
|
2015-04-30 05:11:20 +03:00
|
|
|
echo ${Variable/Some/A}
|
2015-05-26 04:25:07 +03:00
|
|
|
# This will substitute the first occurrence of "Some" with "A"
|
2013-09-22 08:29:05 +04:00
|
|
|
|
2014-02-28 20:24:45 +04:00
|
|
|
# Substring from a variable
|
2015-04-30 05:11:20 +03:00
|
|
|
Length=7
|
|
|
|
echo ${Variable:0:Length}
|
2014-02-28 20:24:45 +04:00
|
|
|
# This will return only the first 7 characters of the value
|
|
|
|
|
2013-12-18 12:37:27 +04:00
|
|
|
# Default value for variable
|
2015-04-30 05:11:20 +03:00
|
|
|
echo ${Foo:-"DefaultValueIfFooIsMissingOrEmpty"}
|
|
|
|
# This works for null (Foo=) and empty string (Foo=""); zero (Foo=0) returns 0.
|
2015-05-02 15:21:03 +03:00
|
|
|
# Note that it only returns default value and doesn't change variable value.
|
2013-12-18 12:37:27 +04:00
|
|
|
|
2014-02-21 02:12:12 +04:00
|
|
|
# Builtin variables:
|
2013-09-22 08:29:05 +04:00
|
|
|
# There are some useful builtin variables, like
|
2015-10-02 17:08:27 +03:00
|
|
|
echo "Last program's return value: $?"
|
2013-09-22 08:29:05 +04:00
|
|
|
echo "Script's PID: $$"
|
2015-10-02 17:08:27 +03:00
|
|
|
echo "Number of arguments passed to script: $#"
|
|
|
|
echo "All arguments passed to script: $@"
|
|
|
|
echo "Script's arguments separated into different variables: $1 $2..."
|
2013-08-18 03:14:00 +04:00
|
|
|
|
|
|
|
# Reading a value from input:
|
|
|
|
echo "What's your name?"
|
2015-04-30 05:11:20 +03:00
|
|
|
read Name # Note that we didn't need to declare a new variable
|
|
|
|
echo Hello, $Name!
|
2013-08-18 02:59:35 +04:00
|
|
|
|
|
|
|
# We have the usual if structure:
|
2013-09-22 18:20:10 +04:00
|
|
|
# use 'man test' for more info about conditionals
|
2016-01-12 02:32:03 +03:00
|
|
|
if [ $Name != $USER ]
|
2013-08-18 02:59:35 +04:00
|
|
|
then
|
2013-12-27 19:21:24 +04:00
|
|
|
echo "Your name isn't your username"
|
2014-08-23 10:54:13 +04:00
|
|
|
else
|
|
|
|
echo "Your name is your username"
|
2013-08-18 02:59:35 +04:00
|
|
|
fi
|
|
|
|
|
2015-10-14 18:40:28 +03:00
|
|
|
# NOTE: if $Name is empty, bash sees the above condition as:
|
2016-01-12 02:32:03 +03:00
|
|
|
if [ != $USER ]
|
2015-10-14 18:40:28 +03:00
|
|
|
# which is invalid syntax
|
|
|
|
# so the "safe" way to use potentially empty variables in bash is:
|
2016-01-12 02:32:03 +03:00
|
|
|
if [ "$Name" != $USER ] ...
|
2015-10-14 18:40:28 +03:00
|
|
|
# which, when $Name is empty, is seen by bash as:
|
2016-01-12 02:32:03 +03:00
|
|
|
if [ "" != $USER ] ...
|
2015-10-14 18:40:28 +03:00
|
|
|
# which works as expected
|
|
|
|
|
2013-09-22 08:06:35 +04:00
|
|
|
# There is also conditional execution
|
2013-12-27 19:21:24 +04:00
|
|
|
echo "Always executed" || echo "Only executed if first command fails"
|
2013-09-22 08:06:35 +04:00
|
|
|
echo "Always executed" && echo "Only executed if first command does NOT fail"
|
2013-08-23 00:26:26 +04:00
|
|
|
|
2014-08-06 22:30:15 +04:00
|
|
|
# To use && and || with if statements, you need multiple pairs of square brackets:
|
2015-10-14 18:40:28 +03:00
|
|
|
if [ "$Name" == "Steve" ] && [ "$Age" -eq 15 ]
|
2014-08-06 22:30:15 +04:00
|
|
|
then
|
2015-04-30 05:11:20 +03:00
|
|
|
echo "This will run if $Name is Steve AND $Age is 15."
|
2014-08-06 22:30:15 +04:00
|
|
|
fi
|
|
|
|
|
2015-10-14 18:40:28 +03:00
|
|
|
if [ "$Name" == "Daniya" ] || [ "$Name" == "Zach" ]
|
2014-08-06 22:30:15 +04:00
|
|
|
then
|
2015-04-30 05:11:20 +03:00
|
|
|
echo "This will run if $Name is Daniya OR Zach."
|
2014-08-06 22:30:15 +04:00
|
|
|
fi
|
|
|
|
|
2013-08-18 03:14:00 +04:00
|
|
|
# Expressions are denoted with the following format:
|
|
|
|
echo $(( 10 + 5 ))
|
|
|
|
|
2015-10-02 17:08:27 +03:00
|
|
|
# Unlike other programming languages, bash is a shell so it works in the context
|
|
|
|
# of a current directory. You can list files and directories in the current
|
2013-12-27 19:21:24 +04:00
|
|
|
# directory with the ls command:
|
2013-08-18 16:25:20 +04:00
|
|
|
ls
|
|
|
|
|
|
|
|
# These commands have options that control their execution:
|
|
|
|
ls -l # Lists every file and directory on a separate line
|
|
|
|
|
|
|
|
# Results of the previous command can be passed to the next command as input.
|
2013-08-19 20:14:02 +04:00
|
|
|
# grep command filters the input with provided patterns. That's how we can list
|
2013-12-27 19:21:24 +04:00
|
|
|
# .txt files in the current directory:
|
2013-08-18 16:25:20 +04:00
|
|
|
ls -l | grep "\.txt"
|
|
|
|
|
2015-10-19 00:20:55 +03:00
|
|
|
# Since bash works in the context of a current directory, you might want to
|
|
|
|
# run your command in some other directory. We have cd for changing location:
|
|
|
|
cd ~ # change to home directory
|
|
|
|
cd .. # go up one directory
|
|
|
|
# (^^say, from /home/username/Downloads to /home/username)
|
|
|
|
cd /home/username/Documents # change to specified directory
|
|
|
|
cd ~/Documents/.. # still in home directory..isn't it??
|
|
|
|
|
|
|
|
|
2014-10-31 03:20:05 +03:00
|
|
|
# You can redirect command input and output (stdin, stdout, and stderr).
|
|
|
|
# Read from stdin until ^EOF$ and overwrite hello.py with the lines
|
|
|
|
# between "EOF":
|
|
|
|
cat > hello.py << EOF
|
|
|
|
#!/usr/bin/env python
|
|
|
|
from __future__ import print_function
|
|
|
|
import sys
|
|
|
|
print("#stdout", file=sys.stdout)
|
|
|
|
print("#stderr", file=sys.stderr)
|
|
|
|
for line in sys.stdin:
|
|
|
|
print(line, file=sys.stdout)
|
|
|
|
EOF
|
|
|
|
|
|
|
|
# Run hello.py with various stdin, stdout, and stderr redirections:
|
|
|
|
python hello.py < "input.in"
|
|
|
|
python hello.py > "output.out"
|
|
|
|
python hello.py 2> "error.err"
|
|
|
|
python hello.py > "output-and-error.log" 2>&1
|
|
|
|
python hello.py > /dev/null 2>&1
|
|
|
|
# The output error will overwrite the file if it exists,
|
|
|
|
# if you want to append instead, use ">>":
|
|
|
|
python hello.py >> "output.out" 2>> "error.err"
|
|
|
|
|
2015-05-12 05:20:02 +03:00
|
|
|
# Overwrite output.out, append to error.err, and count lines:
|
2014-10-31 03:20:05 +03:00
|
|
|
info bash 'Basic Shell Features' 'Redirections' > output.out 2>> error.err
|
|
|
|
wc -l output.out error.err
|
|
|
|
|
|
|
|
# Run a command and print its file descriptor (e.g. /dev/fd/123)
|
|
|
|
# see: man fd
|
|
|
|
echo <(echo "#helloworld")
|
|
|
|
|
2015-05-12 05:20:02 +03:00
|
|
|
# Overwrite output.out with "#helloworld":
|
2014-10-31 03:20:05 +03:00
|
|
|
cat > output.out <(echo "#helloworld")
|
|
|
|
echo "#helloworld" > output.out
|
|
|
|
echo "#helloworld" | cat > output.out
|
|
|
|
echo "#helloworld" | tee output.out >/dev/null
|
|
|
|
|
|
|
|
# Cleanup temporary files verbosely (add '-i' for interactive)
|
|
|
|
rm -v output.out error.err output-and-error.log
|
2013-09-22 18:04:24 +04:00
|
|
|
|
2013-10-04 19:32:11 +04:00
|
|
|
# Commands can be substituted within other commands using $( ):
|
2013-08-19 20:14:02 +04:00
|
|
|
# The following command displays the number of files and directories in the
|
|
|
|
# current directory.
|
2013-08-18 04:33:32 +04:00
|
|
|
echo "There are $(ls | wc -l) items here."
|
|
|
|
|
2013-12-09 16:17:20 +04:00
|
|
|
# The same can be done using backticks `` but they can't be nested - the preferred way
|
|
|
|
# is to use $( ).
|
|
|
|
echo "There are `ls | wc -l` items here."
|
|
|
|
|
2013-10-04 19:32:11 +04:00
|
|
|
# Bash uses a case statement that works similarly to switch in Java and C++:
|
2015-04-30 05:11:20 +03:00
|
|
|
case "$Variable" in
|
2013-08-19 20:14:02 +04:00
|
|
|
#List patterns for the conditions you want to meet
|
2013-08-31 15:35:04 +04:00
|
|
|
0) echo "There is a zero.";;
|
|
|
|
1) echo "There is a one.";;
|
|
|
|
*) echo "It is not null.";;
|
2013-08-18 04:33:32 +04:00
|
|
|
esac
|
|
|
|
|
2013-12-27 19:21:24 +04:00
|
|
|
# for loops iterate for as many arguments given:
|
2015-04-30 05:11:20 +03:00
|
|
|
# The contents of $Variable is printed three times.
|
|
|
|
for Variable in {1..3}
|
2013-08-18 04:33:32 +04:00
|
|
|
do
|
2015-04-30 05:11:20 +03:00
|
|
|
echo "$Variable"
|
2013-08-18 04:33:32 +04:00
|
|
|
done
|
|
|
|
|
2014-09-06 05:51:48 +04:00
|
|
|
# Or write it the "traditional for loop" way:
|
|
|
|
for ((a=1; a <= 3; a++))
|
|
|
|
do
|
|
|
|
echo $a
|
|
|
|
done
|
|
|
|
|
2014-08-08 21:24:43 +04:00
|
|
|
# They can also be used to act on files..
|
|
|
|
# This will run the command 'cat' on file1 and file2
|
2015-04-30 05:11:20 +03:00
|
|
|
for Variable in file1 file2
|
2014-08-08 21:24:43 +04:00
|
|
|
do
|
2015-04-30 05:11:20 +03:00
|
|
|
cat "$Variable"
|
2014-08-08 21:24:43 +04:00
|
|
|
done
|
|
|
|
|
|
|
|
# ..or the output from a command
|
|
|
|
# This will cat the output from ls.
|
2015-04-30 05:11:20 +03:00
|
|
|
for Output in $(ls)
|
2014-08-08 21:24:43 +04:00
|
|
|
do
|
2015-04-30 05:11:20 +03:00
|
|
|
cat "$Output"
|
2014-08-08 21:24:43 +04:00
|
|
|
done
|
|
|
|
|
2013-11-25 19:42:37 +04:00
|
|
|
# while loop:
|
2014-08-08 21:11:17 +04:00
|
|
|
while [ true ]
|
2013-11-25 19:42:37 +04:00
|
|
|
do
|
|
|
|
echo "loop body here..."
|
|
|
|
break
|
|
|
|
done
|
|
|
|
|
2013-09-22 18:28:59 +04:00
|
|
|
# You can also define functions
|
|
|
|
# Definition:
|
2013-10-13 07:14:24 +04:00
|
|
|
function foo ()
|
2013-09-22 18:28:59 +04:00
|
|
|
{
|
|
|
|
echo "Arguments work just like script arguments: $@"
|
|
|
|
echo "And: $1 $2..."
|
|
|
|
echo "This is a function"
|
|
|
|
return 0
|
|
|
|
}
|
|
|
|
|
2013-10-13 07:14:24 +04:00
|
|
|
# or simply
|
|
|
|
bar ()
|
|
|
|
{
|
|
|
|
echo "Another way to declare functions!"
|
|
|
|
return 0
|
|
|
|
}
|
|
|
|
|
2013-09-22 18:28:59 +04:00
|
|
|
# Calling your function
|
2015-04-30 05:11:20 +03:00
|
|
|
foo "My name is" $Name
|
2013-09-22 18:35:04 +04:00
|
|
|
|
|
|
|
# There are a lot of useful commands you should learn:
|
|
|
|
# prints last 10 lines of file.txt
|
2014-07-23 10:32:50 +04:00
|
|
|
tail -n 10 file.txt
|
2013-09-22 18:35:04 +04:00
|
|
|
# prints first 10 lines of file.txt
|
2014-07-23 10:32:50 +04:00
|
|
|
head -n 10 file.txt
|
2013-09-22 18:35:04 +04:00
|
|
|
# sort file.txt's lines
|
2014-07-23 10:32:50 +04:00
|
|
|
sort file.txt
|
2013-09-22 18:35:04 +04:00
|
|
|
# report or omit repeated lines, with -d it reports them
|
2014-07-23 10:32:50 +04:00
|
|
|
uniq -d file.txt
|
2013-09-22 18:35:04 +04:00
|
|
|
# prints only the first column before the ',' character
|
2014-07-23 10:32:50 +04:00
|
|
|
cut -d ',' -f 1 file.txt
|
2014-10-05 01:50:00 +04:00
|
|
|
# replaces every occurrence of 'okay' with 'great' in file.txt, (regex compatible)
|
|
|
|
sed -i 's/okay/great/g' file.txt
|
2015-04-24 00:06:54 +03:00
|
|
|
# print to stdout all lines of file.txt which match some regex
|
|
|
|
# The example prints lines which begin with "foo" and end in "bar"
|
2014-10-05 01:50:00 +04:00
|
|
|
grep "^foo.*bar$" file.txt
|
|
|
|
# pass the option "-c" to instead print the number of lines matching the regex
|
|
|
|
grep -c "^foo.*bar$" file.txt
|
2015-04-24 00:06:54 +03:00
|
|
|
# if you literally want to search for the string,
|
|
|
|
# and not the regex, use fgrep (or grep -F)
|
2015-10-08 06:11:24 +03:00
|
|
|
fgrep "^foo.*bar$" file.txt
|
2014-10-31 03:46:37 +03:00
|
|
|
|
|
|
|
|
|
|
|
# Read Bash shell builtins documentation with the bash 'help' builtin:
|
|
|
|
help
|
|
|
|
help help
|
|
|
|
help for
|
|
|
|
help return
|
|
|
|
help source
|
|
|
|
help .
|
|
|
|
|
|
|
|
# Read Bash manpage documentation with man
|
|
|
|
apropos bash
|
|
|
|
man 1 bash
|
|
|
|
man bash
|
|
|
|
|
|
|
|
# Read info documentation with info (? for help)
|
|
|
|
apropos info | grep '^info.*('
|
|
|
|
man info
|
|
|
|
info info
|
|
|
|
info 5 info
|
|
|
|
|
|
|
|
# Read bash info documentation:
|
|
|
|
info bash
|
|
|
|
info bash 'Bash Features'
|
|
|
|
info bash 6
|
|
|
|
info --apropos bash
|
2013-08-18 04:33:32 +04:00
|
|
|
```
|