1. Log on a Linux machine or connect to one from a Windows machine (e.g.

click
on the Exceed icon and then use putty to connect to the server kiwi. Enter your
login (user name) and password at relevant prompts.
2. Enter these commands at the UNIX prompt, and try to interpret the output. Ask
questions and don't be afraid to experiment (as a normal user you cannot do much
harm):
o echo hello world
o passwd
o date
o hostname
o arch
o uname -a
o dmesg | more (you may need to press q to quit)
o uptime
o who am i
o who
o id
o last
o finger
o w
o top (you may need to press q to quit)
o echo $SHELL
o echo {con,pre}{sent,fer}{s,ed}
o man "automatic door"
o man ls (you may need to press q to quit)
o man who (you may need to press q to quit)
o who can tell me why i got divorced
o lost
o clear
o cal 2000
o cal 9 1752 (do you notice anything unusual?)
o bc -l (type quit or press Ctrl-d to quit)
o echo 5+4 | bc -l
o yes please (you may need to press Ctrl-c to quit)
o time sleep 5
o history

3. Try the following command sequence:

o cd
o pwd
o ls -al
o cd .
o pwd (where did that get you?)
 o cd ..
o pwd
o ls -al
o cd ..
o pwd
o ls -al
o cd ..
o pwd (what happens now)
o cd /etc
o ls -al | more
o cat passwd
o cd -
o pwd
4. Continue to explore the filesystem tree using cd, ls, pwd and cat. Look in /bin, /usr/bin,
/sbin, /tmp and /boot. What do you see?
5. Explore /dev. Can you identify what devices are available? Which are character-oriented
and which are block-oriented? Can you identify your tty (terminal) device (typing who am
i might help); who is the owner of your tty (use ls -l)?
6. Explore /proc. Display the contents of the files interrupts, devices, cpuinfo, meminfo
and uptime using cat. Can you see why we say /proc is a pseudo-filesystem which
allows access to kernel data structures?
7. Change to the home directory of another user directly, using cd ~username.
8. Change back into your home directory.
9. Make subdirectories called work and play.
10. Delete the subdirectory called work.
11. Copy the file /etc/passwd into your home directory.
12. Move it into the subdirectory play.
13. Change into subdirectory play and create a symbolic link called terminal that points to
your tty device. What happens if you try to make a hard link to the tty device?
14. What is the difference between listing the contents of directory play with ls -l and ls
-L?
15. Create a file called hello.txt that contains the words "hello world". Can you use "cp"
using "terminal" as the source file to achieve the same effect?
16. Copy hello.txt to terminal. What happens?
17. Imagine you were working on a system and someone accidentally deleted the ls
command (/bin/ls). How could you get a list of the files in the current directory? Try it.
18. How would you create and then delete a file called " $SHELL"? Try it.
19. How would you create and then delete a file that begins with the symbol #? Try it.
20. How would you create and then delete a file that begins with the symbol -? Try it.
21. What is the output of the command: echo {con,pre}{sent,fer}{s,ed}? Now, from your
home directory, copy /etc/passwd and /etc/group into your home directory in one
command given that you can only type /etc once.
22. Still in your home directory, copy the entire directory play to a directory called work,
preserving the symbolic link.
 23. Delete the work directory and its contents with one command. Accept no complaints or
queries.
24. Change into a directory that does not belong to you and try to delete all the files (avoid
/proc or /dev, just in case!)

25. Experiment with the options on the ls command. What do the d, i, R and F options do?

/////////////////////////////////////////////////////////////////////////////////////////////////////////////

1. Describe three different ways of setting the permissions on a file or directory to

r--r--r--. Create a file and see if this works.
2. Team up with a partner. Copy /bin/sh to your home directory. Type "chmod +s
sh". Check the permissions on sh in the directory listing. Now ask your partner to
change into your home directory and run the program ./sh. Ask them to run the
id command. What's happened? Your partner can type exit to return to their
shell.
3. What would happen if the system administrator created a sh file in this way? Why
is it sometimes necessary for a system administrator to use this feature using
programs other than sh?
4. Delete sh from your home directory (or at least to do a chmod -s sh).
5. Modify the permissions on your home directory to make it completely private.
Check that your partner can't access your directory. Now put the permissions back
to how they were.
6. Type umask 000 and then create a file called world.txt containing the words
"hello world". Look at the permissions on the file. What's happened? Now type
umask 022 and create a file called world2.txt. When might this feature be useful?
7. Create a file called "hello.txt" in your home directory using the command cat
-u > hello.txt. Ask your partner to change into your home directory and run
tail -f hello.txt. Now type several lines into hello.txt. What appears on your
partner's screen?
8. Use find to display the names of all files in the /home subdirectory tree. Can you
do this without displaying errors for files you can't read?
9. Use find to display the names of all files in the system that are bigger than 1MB.
10. Use find and file to display all files in the /home subdirectory tree, as well as a
guess at what sort of a file they are. Do this in two different ways.
11. Use grep to isolate the line in /etc/passwd that contains your login details.
12. Use find and grep and sort to display a sorted list of all files in the /home
subdirectory tree that contain the word hello somewhere inside them.
13. Use locate to find all filenames that contain the word emacs. Can you combine
this with grep to avoid displaying all filenames containing the word lib?
14. Create a file containing some lines that you think would match the regular
expression: (^[0-9]{1,5}[a-zA-z ]+$)|none and some lines that you think would
not match. Use egrep to see if your intuition is correct.
 15. Archive the contents of your home directory (including any subdirectories) using
tar and cpio. Compress the tar archive with compress, and the cpio archive with
gzip. Now extract their contents.
16. On Linux systems, the file /dev/urandom is a constantly generated random stream
of characters. Can you use this file with od to printout a random decimal number?

17. Type mount (with no parameters) and try to interpret the output.

////////////////////////////////////////////////////////////////////////////////////////////////////////////

1. Archive the contents of your home directory using tar. Compress the tar file with
gzip. Now uncompress and unarchive the .tar.gz file using cat, tar and gzip on
one command line.
2. Use find to compile a list of all directories in the system, redirecting the output so
that the list of directories ends up in a file called directories.txt and the list of
error messages ends up in a file called errors.txt.
3. Try the command sleep 5. What does this command do?
4. Run the command in the background using &.
5. Run sleep 15 in the foreground, suspend it with Ctrl-z and then put it into the
background with bg. Type jobs. Type ps. Bring the job back into the foreground
with fg.
6. Run sleep 15 in the background using &, and then use kill to terminate the
process by its job number. Repeat, except this time kill the process by specifying
its PID.
7. Run sleep 15 in the background using &, and then use kill to suspend the
process. Use bg to continue running the process.
8. Startup a number of sleep 60 processes in the background, and terminate them all
at the same time using the pkill command.
9. Use ps, w and top to show all processes that are executing.
10. Use ps -aeH to display the process hierarchy. Look for the init process. See if
you can identify important system daemons. Can you also identify your shell and
its subprocesses?
11. Combine ps -fae with grep to show all processes that you are executing, with the
exception of the ps -fae and grep commands.
12. Start a sleep 300 process running in the background. Log off the server, and log
back in again. List all the processes that you are running. What happened to your
sleep process? Now repeat, except this time start by running nohup sleep 300.
13. Multiple jobs can be issued from the same command line using the operators ;, &&
and ||. Try combining the commands cat nonexistent and echo hello using each
of these operators. Reverse the order of the commands and try again. What are the
rules about when the commands will be executed?
14. What does the xargs command do? Can you combine it with find and grep to find
yet another way of searching all files in the /home subdirectory tree for the word
hello?
 15. What does the cut command do? Can you use it together with w to produce a list
of login names and CPU times corresponding to each active process? Can you
now (all on the same command line) use sort and head or tail to find the user
whose process is using the most CPU?

///////////////////////////////////////////////////////////////////////////////////////////////////////////

1. Use telnet to request a web page from the web server www.doc.ic.ac.uk by
connecting to port 80, as shown in the notes.
2. Use ping to find the round-trip delay to www.altavista.com.
3. Use traceroute to see the network route taken to www.altavista.com (which is in
the USA). Can you tell which cities your network traffic passes through?
4. Use ftp to connect to the FTP site sunsite.doc.ic.ac.uk. Obtain the latest
version of the package units (in the form of a .tar.gz file) from the directory
packages/gnu/units. Decompress and unarchive the .tar.gz file. Type configure
and then make. Run the executable program that is produced as " ./units -f
units.dat". What does the program do? If you were the system administrator,
what would you have to do to install the package for everyone to use?
5. Use wget to get a copy of the web page http://www.doc.ic.ac.uk/index.html.
Have a look at the contents of the file. Can you use sed to strip out the
HTML tags (text enclosed in < and >) to leave you with just plain text?
6. Use finger or who to get a list of users on the machine.
7. Use write to send them a message. To stop people from sending you messages,
type "mesg n". To reenable messages, type "mesg y".
8. Try use talk to send a message to someone (N.B. this may not work).
9. List all your processes, using sed to substitute "me" for your username.
10. Use who, awk, sort and uniq to print out a sorted list of the logins of active users.
11. Use awk on /etc/passwd to produce a list of users and their login shells.
12. Write an awk script that prints out all lines in a file except for the first two.
13.Modify the awk script in the notes so that it doesn't increase the number of
players used to calculate the average if the manner of dismissal is "not-out".
14. Create a file called hello.c containing the simple "hello world" program in the
notes. Create an appropriate makefile for compiling it. Run make.

15. Use man -k to find a suitable utility for viewing postscript files.

////////////////////////////////////////////////////////////////////////////////////////////////////////

1. Copy the file mole.txt into your home directory (press shift and the left mouse
button to download the file using Netscape).
2. Edit your copy of the document using vi.
3. Go to the end of the document and type in the following paragraph:

Joined the library. Got Care of the Skin, Origin of the Species, and a
book by a woman my mother is always going on about. It is called Pride and
Prejudice, by a woman called Jane Austen. I could tell the librarian was
 impressed. Perhaps she is an intellectual like me. She didn't look at my
spot, so perhaps it is getting smaller.
4. Correct the three spelling errors in the first three lines of the first paragraph (one
error per line) and remove the extra "Geography" in the 3rd line of the first
paragraph.
5. Add the words "About time!" to the end of the second paragraph.
6. Delete the sentence "Time flies like an arrow but fruit flies like a
banana" and re-form the paragraph.
7. Replace all occurrences of "is" with "was".
8. Swap the two paragraphs.
9. Save the file and quit.
10. Repeat the exercise with emacs. Which did you find easier?
11. Can you write a simple C program (say the hello world program) and makefile,
compile and run it - all from inside emacs?

12. If you'd like an indepth vi tutorial try running "vimtutor". For an indepth emacs
tutorial, type M-x help-with-tutorial from inside emacs.

/////////////////////

Wednesday January 14th

None of the teechers at school have noticed that I am an intellectual. They

will be sorry when I am famouse. There is a new girl in our class. She sits
nixt to me in Geography Geography.
Time flies like an arrow but fruit flies like a banana.
She is all right. Her name is Pandora, but she likes being called "Box".
Don't ask me why. I might fall in love with her. It's time I fell in love,
after all I am 13 3/4 years old.

////////////////////////////////////////////////////////////////////////////////////////////////////

N.B. Please perform these tasks on your home PC and take extra care when using the root
account. Since your commands will be carried out without the safeguards that apply to ordinary
users, you may do serious damage to the system. If in doubt, please ask (preferably before
pressing !)

1. Use su - to become root.

2. Add a new user of your choosing to the system. Set their password. Check that
they can log in.
3. Add a new user group of your choosing to the system. Place yourself (i.e. your
login, not root), and the user that you have added in the group. Check that you are
both in the new group.
4. Remove the user that you added.
5. Make yourself a cron job that sends you a message (using write) every 10
minutes. Remove this when you start to find it irritating.
6. Discover how to restart the web server httpd (or any other system daemon).
 7. tinyhttpd.pl is a mini-web server written in Perl. Switch back to being a
normal user, and make a copy of tinyhttpd.pl in your home directory. Change
the port number on which it operates to a port of your choice (currently 8080, but
use a different one that noone else will be using). Create a public_html directory
in your home directory and create a home page file inside it called " index.html".
Now run tinyhttpd.pl in the background and use telnet (telnet machine port,
where machine is the hostname and port is the port number, and then issue the
HTTP command GET / HTTP/1.0 ) or a web browser (call up
http://machine:port) to test that your home page file is in fact being served.

8. Switch back to being root. Add a line to /etc/inittab which will ensure that your
mini web-server will respawn itself if it dies. Kill your web server (using kill)
and see if the respawning works (init re-examines the /etc/inittab file
whenever one of its descendant processes dies so you should not have long to wait
for this to take effect). It may be helpful to monitor the system messages file with
tail -f /var/log/messages.

//////////////////////////////////////////////////////////////////////////////////////

1. Use your favourite UNIX editor to create the simple shell script given in Section
8.4 of the notes. Run it, and see how the contents of the script relates to the
output.
2. Extend the script so that it generates a random secret number between 1 and 100
(c.f. Exercise Sheet 3, Question 16) and then keeps asking the user to guess the
secret number until they guess correctly. The script should give the user hints
such as "I'm sorry your guess is too low" or "I'm sorry your guess is too high".
3. Write a shell script which renames all .txt files as .text files. The command
basename might help you here.
4. Write a shell script called pidof which takes a name as parameter and returns the
PID(s) of processes with that name.
5. Shell scripts can also include functions. Functions are declared as:

function funcname() {
statements
}

and invoked as funcname param1 param2... The parameters passed to the

function are accessible inside the function through the variables $1, $2, etc. Now
add a usage() function to your pidof script which prints usage instructions. Call
usage() if the wrong number of parameters is passed to the script.

6. Modify your .bash_profile script so that your PATH includes the current directory
(.) and so that your environment variable EDITOR is set to emacs or vi (or whatever
else you prefer to use). Run the modified script using source .bash_profile and
check that the changes you made have been applied to the current shell (type set).
//////////////////////////////////////////////////////////////////////////////////////////////////////////////

Introduction to UNIX:
Lecture Eight
8.1 Objectives
This chapter covers:

• Shells and shell scripts.

• Shells variables and the environment.
• Simple shell scripting
• Advanced shell scripting.
• Start-up shell scripts.

8.2 Shells and Shell Scripts

A shell is a program which reads and executes commands for the user. Shells also usually
provide features such job control, input and output redirection and a command language for
writing shell scripts. A shell script is simply an ordinary text file containing a series of
commands in a shell command language (just like a "batch file" under MS-DOS).

There are many different shells available on UNIX systems (e.g. sh, bash, csh, ksh, tcsh etc.),
and they each support a different command language. Here we will discuss the command
language for the Bourne shell sh since it is available on almost all UNIX systems (and is also
supported under bash and ksh).

8.3 Shell Variables and the Environment

A shell lets you define variables (like most programming languages). A variable is a piece of
data that is given a name. Once you have assigned a value to a variable, you access its value by
prepending a $ to the name:

$ bob='hello world'
$ echo $bob
hello world
$
Variables created within a shell are local to that shell, so only that shell can access them. The
set command will show you a list of all variables currently defined in a shell. If you wish a
variable to be accessible to commands outside the shell, you can export it into the environment:

$ export bob

(under csh you used setenv). The environment is the set of variables that are made available to
commands (including shells) when they are executed. UNIX commands and programs can read
the values of environment variables, and adjust their behaviour accordingly. For example, the
environment variable PAGER is used by the man command (and others) to see what command
should be used to display multiple pages. If you say:

$ export PAGER=cat

and then try the man command (say man pwd), the page will go flying past without stopping. If
you now say:

$ export PAGER=more

normal service should be resumed (since now more will be used to display the pages one at a
time). Another environment variable that is commonly used is the EDITOR variable which
specifies the default editor to use (so you can set this to vi or emacs or which ever other editor
you prefer). To find out which environment variables are used by a particular command,
consult the man pages for that command.

Another interesting environment variable is PS1, the main shell prompt string which you can
use to create your own custom prompt. For example:

$ export PS1="(\h) \w> "

(lumberjack) ~>

The shell often incorporates efficient mechanisms for specifying common parts of the shell
prompt (e.g. in bash you can use \h for the current host, \w for the current working directory, \d
for the date, \t for the time, \u for the current user and so on - see the bash man page).

Another important environment variable is PATH. PATH is a list of directories that the shell uses
to locate executable files for commands. So if the PATH is set to:

/bin:/usr/bin:/usr/local/bin:.

and you typed ls, the shell would look for /bin/ls, /usr/bin/ls etc. Note that the PATH
contains'.', i.e. the current working directory. This allows you to create a shell script or
program and run it as a command from your current directory without having to explicitly say
"./filename".
Note that PATH has nothing to with filenames that are specified as arguments to commands (e.g.
cat myfile.txt would only look for ./myfile.txt, not for /bin/myfile.txt,
/usr/bin/myfile.txt etc.)

8.4 Simple Shell Scripting

Consider the following simple shell script, which has been created (using an editor) in a text
file called simple:

#!/bin/sh
# this is a comment
echo "The number of arguments is $#"
echo "The arguments are $*"
echo "The first is $1"
echo "My process number is $$"
echo "Enter a number from the keyboard: "
read number
echo "The number you entered was $number"

The shell script begins with the line " #!/bin/sh" . Usually "#" denotes the start of a comment,
but #! is a special combination that tells UNIX to use the Bourne shell ( sh) to interpret this
script. The #! must be the first two characters of the script. The arguments passed to the script
can be accessed through $1, $2, $3 etc. $* stands for all the arguments, and $# for the number of
arguments. The process number of the shell executing the script is given by $$. the read
number statement assigns keyboard input to the variable number.

To execute this script, we first have to make the file simple executable:

$ ls -l simple
-rw-r--r-- 1 will finance 175 Dec 13 simple
$ chmod +x simple
$ ls -l simple
-rwxr-xr-x 1 will finance 175 Dec 13 simple
$ ./simple hello world
The number of arguments is 2
The arguments are hello world
The first is hello
My process number is 2669
Enter a number from the keyboard:
5
The number you entered was 5
$

We can use input and output redirection in the normal way with scripts, so:
 $ echo 5 | simple hello world

would produce similar output but would not pause to read a number from the keyboard.

8.5 More Advanced Shell Scripting

• if-then-else statements

Shell scripts are able to perform simple conditional branches:

if [test ]
then
commands-if-test-is-true
else
commands-if-test-is-false
fi

The test condition may involve file characteristics or simple string or numerical
comparisons. The [ used here is actually the name of a command ( /bin/[) which
performs the evaluation of the test condition. Therefore there must be spaces
before and after it as well as before the closing bracket. Some common test
conditions are:

-s file
true if file exists and is not empty
-f file
true if file is an ordinary file
-d file
true if file is a directory
-r file
true if file is readable
-w file
true if file is writable
-x file
true if file is executable
$X -eq $Y
true if X equals Y
$X -ne $Y
true if X not equal to Y
$X -lt $Y
true if X less than $Y
$X -gt $Y
true if X greater than $Y
$X -le $Y
 true if X less than or equal to Y
$X -ge $Y
true if X greater than or equal to Y
"$A" = "$B"
true if string A equals string B
"$A" != "$B"
true if string A not equal to string B
$X ! -gt $Y
true if string X is not greater than Y
$E -a $F
true if expressions E and F are both true
$E -o $F
true if either expression E or expression F is true

• for loops

Sometimes we want to loop through a list of files, executing some commands on

each file. We can do this by using a for loop:

for variable in list

do
statements (referring to $variable)
done

The following script sorts each text files in the current directory :

#!/bin/sh
for f in *.txt
do
echo sorting file $f
cat $f | sort > $f.sorted
echo sorted file has been output to $f.sorted
done

• while loops

Another form of loop is the while loop:

while [ test ]
do
statements (to be executed while test is true)
done

The following script waits until a non-empty file input.txt has been created:
 #!/bin/sh
while [ ! -s input.txt ]
do
echo waiting...
sleep 5
done
echo input.txt is ready

You can abort a shell script at any point using the exit statement, so the following
script is equivalent:

#!/bin/sh
while true
do
if [ -s input.txt ]
echo input.txt is ready
exit
fi
echo waiting...
sleep 5
done

• case statements

case statements are a convenient way to perform multiway branches where one
input pattern must be compared to several alternatives:

casevariable in
pattern1)
statement (executed if variable matches pattern1)
;;
pattern2)
statement
;;
etc.
esac

The following script uses a case statement to have a guess at the type of non-
directory non-executable files passed as arguments on the basis of their extensions
(note how the "or" operator | can be used to denote multiple patterns, how " *" has
been used as a catch-all, and the effect of the forward single quotes `):

#!/bin/sh
for f in $*
do
 if [ -f $f -a ! -x $f ]
then
case $f in
core)
echo "$f: a core dump file"
;;
*.c)
echo "$f: a C program"
;;
*.cpp|*.cc|*.cxx)
echo "$f: a C++ program"
;;
*.txt)
echo "$f: a text file"
;;
*.pl)
echo "$f: a PERL script"
;;
*.html|*.htm)
echo "$f: a web document"
;;
*)
echo "$f: appears to be "`file -b $f`
;;
esac
fi
done

• capturing command output

Any UNIX command or program can be executed from a shell script just as if you
would on the line command line. You can also capture the output of a command
and assign it to a variable by using the forward single quotes ` `:

#!\bin\sh
lines=`wc -l $1`
echo "the file $1 has $lines lines"

This script outputs the number of lines in the file passed as the first parameter.

• arithmetic operations

The Bourne shell doesn't have any built-in ability to evaluate simple mathematical
expressions. Fortunately the UNIX expr command is available to do this. It is
 frequently used in shell scripts with forward single quotes to update the value of a
variable. For example:

lines = `expr $lines + 1`

adds 1 to the variable lines. expr supports the operators +, -, *, /, % (remainder),

<, <=, =, !=, >=, >, | (or) and & (and).

8.6 Start-up Shell Scripts

When you first login to a shell, your shell runs a systemwide start-up script (usually called
/etc/profile under sh, bash and ksh and /etc/.login under csh). It then looks in your home
directory and runs your personal start-up script ( .profile under sh, bash and ksh and .cshrc
under csh and tcsh). Your personal start-up script is therefore usually a good place to set up
environment variables such as PATH, EDITOR etc. For example with bash, to add the directory
~/bin to your PATH, you can include the line:

export PATH=$PATH:~/bin

in your .profile. If you subsequently modify your .profile and you wish to import the
changes into your current shell, type:

$ source .profile
or
$ . ./profile

The source command is built into the shell. It ensures that changes to the environment made in
.profile affect the current shell, and not the shell that would otherwise be created to execute
the .profile script.

With csh, to add the directory ~/bin to your PATH, you can include the line:

set path = ( $PATH $HOME/bin )

in your .cshrc.

(BACK TO COURSE CONTENTS)

© September 2001 William Knottenbelt ([email protected])