UNIX shell environments CS 2204 Class meeting 6 *Notes by Doug Bowman and other members of the CS...

18
UNIX shell environments CS 2204 Class meeting 6 *Notes by Doug Bowman and other members of the CS faculty at Virginia Tech. Copyright 2001-2003.

Transcript of UNIX shell environments CS 2204 Class meeting 6 *Notes by Doug Bowman and other members of the CS...

Page 1: UNIX shell environments CS 2204 Class meeting 6 *Notes by Doug Bowman and other members of the CS faculty at Virginia Tech. Copyright 2001-2003.

UNIX shell environments

CS 2204

Class meeting 6

*Notes by Doug Bowman and other members of the CS faculty at Virginia Tech. Copyright 2001-2003.

Page 2: UNIX shell environments CS 2204 Class meeting 6 *Notes by Doug Bowman and other members of the CS faculty at Virginia Tech. Copyright 2001-2003.

(C) Doug Bowman, Virginia Tech, 2001 2

Shell characteristics Command line interface between the user

and the system Is simply a program that automatically

starts when you login Waits for user to type in commands

Page 3: UNIX shell environments CS 2204 Class meeting 6 *Notes by Doug Bowman and other members of the CS faculty at Virginia Tech. Copyright 2001-2003.

(C) Doug Bowman, Virginia Tech, 2001 3

Main shell features Interactivity

aliases file-name completion

Scripting language Allows programming (shell scripting) within

the shell environment Uses variables, loops, conditionals, etc. Next lecture

Page 4: UNIX shell environments CS 2204 Class meeting 6 *Notes by Doug Bowman and other members of the CS faculty at Virginia Tech. Copyright 2001-2003.

(C) Doug Bowman, Virginia Tech, 2001 4

Various UNIX shells sh (Bourne shell, original UNIX shell) ksh (Korn shell) csh (C shell, developed at Berkeley) tcsh bash (Bourne again SHell) … Differences mostly in level of interactivity

support and scripting details

Page 5: UNIX shell environments CS 2204 Class meeting 6 *Notes by Doug Bowman and other members of the CS faculty at Virginia Tech. Copyright 2001-2003.

(C) Doug Bowman, Virginia Tech, 2001 5

The Bourne again SHell (bash) We will be using bash and ksh as the

standard shells for this class This will be important for shell scripting

assignments Superset of the Bourne shell (sh) Borrows features from sh, csh, tcsh & ksh Created by Free Software Foundation

Page 6: UNIX shell environments CS 2204 Class meeting 6 *Notes by Doug Bowman and other members of the CS faculty at Virginia Tech. Copyright 2001-2003.

(C) Doug Bowman, Virginia Tech, 2001 6

Changing your shell On most UNIX machines (and lab):

which bash (note path) chsh

On the some machines: which ksh (note path /bin/bash) ypchsh

Page 7: UNIX shell environments CS 2204 Class meeting 6 *Notes by Doug Bowman and other members of the CS faculty at Virginia Tech. Copyright 2001-2003.

(C) Doug Bowman, Virginia Tech, 2001 7

Environment variables A set of variables the shell uses for

certain operations Variables have a name and a value Current list can be displayed with the env

command A particular variable’s value can be

displayed with echo $<var_name>

Page 8: UNIX shell environments CS 2204 Class meeting 6 *Notes by Doug Bowman and other members of the CS faculty at Virginia Tech. Copyright 2001-2003.

(C) Doug Bowman, Virginia Tech, 2001 8

Some Environment variables Some interesting variables: HOME, PATH, PS1, USER, HOSTNAME, PWD

$HOME /home/gradstudents/m/miali

$PATH /usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin

$PS1 \u@\h:\w\$

$USER sgifford

$HOSTNAME avocado.cslab.vt.edu

$PWD /home/grads/sgifford

Page 9: UNIX shell environments CS 2204 Class meeting 6 *Notes by Doug Bowman and other members of the CS faculty at Virginia Tech. Copyright 2001-2003.

(C) Doug Bowman, Virginia Tech, 2001 9

Setting environment variables Set a variable with <name>=<value> Examples:

TERM=vt100 PS1=myprompt> PS1=$USER@$HOSTNAME: PS1=“multiple word prompt> “ PATH=$PATH:$HOME/bin PATH=$PATH:~ DATE=`date`

Page 10: UNIX shell environments CS 2204 Class meeting 6 *Notes by Doug Bowman and other members of the CS faculty at Virginia Tech. Copyright 2001-2003.

(C) Doug Bowman, Virginia Tech, 2001 10

Aliases Aliases are used as shorthand for frequently-

used commands Syntax: alias <shortcut>=<command> Examples:

alias ll=“ls -lF” alias la=“ls -la” alias m=more alias up=“cd ..” alias prompt=“echo $PS1”

Page 11: UNIX shell environments CS 2204 Class meeting 6 *Notes by Doug Bowman and other members of the CS faculty at Virginia Tech. Copyright 2001-2003.

(C) Doug Bowman, Virginia Tech, 2001 11

Repeating commands Use history to list the last 16

commands Use fc -l <m> <n> to list previously

typed commands m through n

Page 12: UNIX shell environments CS 2204 Class meeting 6 *Notes by Doug Bowman and other members of the CS faculty at Virginia Tech. Copyright 2001-2003.

(C) Doug Bowman, Virginia Tech, 2001 12

Editing on the command line Some command lines can be very long and

complicated - if you make a mistake you don’t want to start all over again

You can interactively edit the command line in several ways if using ksh set -o vi allows you to use vi commands to edit

the command line set -o vi-tabcomplete also lets you complete

commands/filenames by entering a TAB

Page 13: UNIX shell environments CS 2204 Class meeting 6 *Notes by Doug Bowman and other members of the CS faculty at Virginia Tech. Copyright 2001-2003.

(C) Doug Bowman, Virginia Tech, 2001 13

Login scripts You don’t want to enter aliases, set

environment variables, set up command line editing, etc. each time you log in

All of these things can be done in a script that is run each time the shell is started

Page 14: UNIX shell environments CS 2204 Class meeting 6 *Notes by Doug Bowman and other members of the CS faculty at Virginia Tech. Copyright 2001-2003.

(C) Doug Bowman, Virginia Tech, 2001 14

Login scripts (continued) For bash, order of files is:

/etc/profile ~/.bash_profile ~/.bash_login ~/.profile

After logout ~/.bash_logout

Page 15: UNIX shell environments CS 2204 Class meeting 6 *Notes by Doug Bowman and other members of the CS faculty at Virginia Tech. Copyright 2001-2003.

(C) Doug Bowman, Virginia Tech, 2001 15

Example .bash_profile (partial)# .bash_profile: executed by bash(1) for login

shellsumask 022

# include .bashrc if it exists

if [ -f ~/.bashrc ]; then source ~/.bashrcfi# some ls aliasesalias ll='ls -l'alias la='ls -A'alias l='ls -CF'

Page 16: UNIX shell environments CS 2204 Class meeting 6 *Notes by Doug Bowman and other members of the CS faculty at Virginia Tech. Copyright 2001-2003.

(C) Doug Bowman, Virginia Tech, 2001 16

Login scripts (continued) For ksh, login shells execute:

~/.profile If ENV is set:

That file is executed for each new terminal Example: ENV=$HOME/.kshrc EXPORT ENV

Page 17: UNIX shell environments CS 2204 Class meeting 6 *Notes by Doug Bowman and other members of the CS faculty at Virginia Tech. Copyright 2001-2003.

(C) Doug Bowman, Virginia Tech, 2001 17

Background processing Allows you to run your programs in the

background sgifford@avocado:~/cs2204/$ emacs vi_practice_edited &

sgifford@avocado:~/cs2204/$

Page 18: UNIX shell environments CS 2204 Class meeting 6 *Notes by Doug Bowman and other members of the CS faculty at Virginia Tech. Copyright 2001-2003.

(C) Doug Bowman, Virginia Tech, 2001 18

stdin, stdout, and stderr Each shell (and in fact all

programs) automatically open three “files” when they start up Standard input (stdin): Usually

from the keyboard Standard output (stdout): Usually

to the terminal Standard error (stderr): Usually to

the terminal

Program comman

d

stdin

stdout

Programs use these three files when reading (e.g. cin, writing (e.g. cout), or reporting errors/diagnostics