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.

2. (C) Doug Bowman, Virginia Tech, 20012 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

3. (C) Doug Bowman, Virginia Tech, 20013 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

4. (C) Doug Bowman, Virginia Tech, 20014 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

5. (C) Doug Bowman, Virginia Tech, 20015 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

6. (C) Doug Bowman, Virginia Tech, 20016 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

7. (C) Doug Bowman, Virginia Tech, 20017 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 $

8. (C) Doug Bowman, Virginia Tech, 20018 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

9. (C) Doug Bowman, Virginia Tech, 20019 Setting environment variables Set a variable with = Examples: TERM=vt100 PS1=myprompt> PS1=$USER@$HOSTNAME: PS1=“multiple word prompt> “ PATH=$PATH:$HOME/bin PATH=$PATH:~ DATE=`date`

10. (C) Doug Bowman, Virginia Tech, 200110 Aliases Aliases are used as shorthand for frequently- used commands Syntax: alias = Examples: alias ll=“ls -lF” alias la=“ls -la” alias m=more alias up=“cd..” alias prompt=“echo $PS1”

11. (C) Doug Bowman, Virginia Tech, 200111 Repeating commands Use history to list the last 16 commands Use fc -l to list previously typed commands m through n

12. (C) Doug Bowman, Virginia Tech, 200112 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

13. (C) Doug Bowman, Virginia Tech, 200113 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

14. (C) Doug Bowman, Virginia Tech, 200114 Login scripts (continued) For bash, order of files is: /etc/profile ~/.bash_profile ~/.bash_login ~/.profile After logout ~/.bash_logout

15. (C) Doug Bowman, Virginia Tech, 200115 Example.bash_profile (partial) #.bash_profile: executed by bash(1) for login shells umask 022 # include.bashrc if it exists if [ -f ~/.bashrc ]; then source ~/.bashrc fi # some ls aliases alias ll='ls -l' alias la='ls -A' alias l='ls -CF'

16. (C) Doug Bowman, Virginia Tech, 200116 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

17. (C) Doug Bowman, Virginia Tech, 200117 Background processing Allows you to run your programs in the background sgifford@avocado:~/cs2204/$ emacs vi_practice_edited & sgifford@avocado:~/cs2204/$

18. (C) Doug Bowman, Virginia Tech, 200118 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 command stdin stdout Programs use these three files when reading (e.g. cin, writing (e.g. cout ), or reporting errors/diagnostics