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"]
|
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:
|
|
|
|
VARIABLE="Some string"
|
|
|
|
|
|
|
|
# But not like this:
|
2013-08-19 20:14:02 +04:00
|
|
|
VARIABLE = "Some string"
|
|
|
|
# Bash will decide that VARIABLE is a command it must execute and give an error
|
|
|
|
# because it couldn't be found.
|
2013-08-18 02:59:35 +04:00
|
|
|
|
|
|
|
# Using the variable:
|
|
|
|
echo $VARIABLE
|
|
|
|
echo "$VARIABLE"
|
2013-09-22 08:29:05 +04:00
|
|
|
echo '$VARIABLE'
|
2013-08-19 20:14:02 +04:00
|
|
|
# When you use the variable itself — assign it, export it, or else — you write
|
|
|
|
# its name without $. If you want to use 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
|
|
|
|
echo ${VARIABLE/Some/A}
|
|
|
|
# This will substitute the first occurance of "Some" with "A"
|
|
|
|
|
2014-02-28 20:24:45 +04:00
|
|
|
# Substring from a variable
|
|
|
|
echo ${VARIABLE:0:7}
|
|
|
|
# This will return only the first 7 characters of the value
|
|
|
|
|
2013-12-18 12:37:27 +04:00
|
|
|
# Default value for variable
|
|
|
|
echo ${FOO:-"DefaultValueIfFOOIsMissingOrEmpty"}
|
|
|
|
# This works for null (FOO=), empty string (FOO=""), zero (FOO=0) returns 0
|
|
|
|
|
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
|
|
|
|
echo "Last program return value: $?"
|
|
|
|
echo "Script's PID: $$"
|
|
|
|
echo "Number of arguments: $#"
|
|
|
|
echo "Scripts arguments: $@"
|
2013-12-27 19:21:24 +04:00
|
|
|
echo "Scripts arguments seperated in different variables: $1 $2..."
|
2013-08-18 03:14:00 +04:00
|
|
|
|
|
|
|
# Reading a value from input:
|
|
|
|
echo "What's your name?"
|
2013-12-27 19:21:24 +04:00
|
|
|
read NAME # Note that we didn't need to declare a new variable
|
2013-08-18 03:14:00 +04:00
|
|
|
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
|
|
|
|
if [ $NAME -ne $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
|
|
|
|
|
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:
|
|
|
|
if [ $NAME == "Steve" ] && [ $AGE -eq 15 ]
|
|
|
|
then
|
|
|
|
echo "This will run if $NAME is Steve AND $AGE is 15."
|
|
|
|
fi
|
|
|
|
|
|
|
|
if [ $NAME == "Daniya" ] || [ $NAME == "Zach" ]
|
|
|
|
then
|
|
|
|
echo "This will run if $NAME is Daniya OR Zach."
|
|
|
|
fi
|
|
|
|
|
2013-08-18 03:14:00 +04:00
|
|
|
# Expressions are denoted with the following format:
|
|
|
|
echo $(( 10 + 5 ))
|
|
|
|
|
2013-08-19 20:14:02 +04:00
|
|
|
# Unlike other programming languages, bash is a shell — so it works in a context
|
|
|
|
# of 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"
|
|
|
|
|
2013-12-27 19:21:24 +04:00
|
|
|
# You can also redirect a command, input and error output.
|
2013-09-22 18:04:24 +04:00
|
|
|
python2 hello.py < "input.in"
|
|
|
|
python2 hello.py > "output.out"
|
|
|
|
python2 hello.py 2> "error.err"
|
|
|
|
# The output error will overwrite the file if it exists, if you want to
|
|
|
|
# concatenate them, use ">>" instead.
|
|
|
|
|
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++:
|
2013-08-31 15:35:04 +04: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:
|
2014-08-08 21:24:29 +04:00
|
|
|
# The contents of $VARIABLE is printed three times.
|
2013-12-09 16:17:20 +04:00
|
|
|
for VARIABLE in {1..3}
|
2013-08-18 04:33:32 +04:00
|
|
|
do
|
2013-08-19 20:14:02 +04: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
|
|
|
|
for VARIABLE in file1 file2
|
|
|
|
do
|
|
|
|
cat "$VARIABLE"
|
|
|
|
done
|
|
|
|
|
|
|
|
# ..or the output from a command
|
|
|
|
# This will cat the output from ls.
|
|
|
|
for OUTPUT in $(ls)
|
|
|
|
do
|
|
|
|
cat "$OUTPUT"
|
|
|
|
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
|
|
|
|
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
|
2013-08-18 04:33:32 +04:00
|
|
|
```
|