Linux Workshop

Lab 2 Command line

Requirements Quick Reference Objectives to learn
➢ Live Linux Command line knowledge
#program files do not need an extension such as .exe
#directories use / instead of \ #(often no drive letters, but) mount points.
#commands & filenames are case sensitive
#help with: cmd --help
#prefix ./ to start a program located in the current directory
#.files are hidden (starting with a dot)

command -options parameters #General command syntax

...<tab> #Automatic cmd completion (WinXP)
...<tab><tab> #Completion for cmd & file choices
...<page up> #Browse through cmd history ( bash)
To Do from the command line
history #Show personal cmd line history
1. Go to the tmp directory !5 #Start command 5 from history

2. How many commands can a user execute? cmd1 ; cmd2 #Use ; for cmd concatenation
#man, info, which, type, whereis, apropos
3. How many commands can a priviliged user ls /etc ¦ less #less is more (<q> to quit)
execute? ls /etc ¦ grep -i fstab #Filter output using grep ignoring upper case
4. How many commands did the user already nohup cmd #Leave cmd running aft logout (hang up)
execute in the past? #such as the screen package
cmd & #Start cmd in background (running)
5. Execute command number 1 from the command <ctrl-z> #Set program into background (stopped)
history
jobs #Show background programs
6. How can you search in a directory to a filename bg [nr] #Start background program (running)
ignoring upper and lower case characters? xset -b #Set sound bell for alerts = off (in X)

7. Change the prompt. Change \w in \W or reverse.

echo $PS #Show prompt string variable
export PS= #Set prompt string variable

Theory Modules
LPIC 1 Certification Bible, isbn 0-7645-4772-0
➢ p. 63 Ch. 2 Using the Shell
➢ p. 275 Ch. 7 Using Documentation
➢ p. 72-77 Environment Variables and Settings
➢ p. 527-540 Customizing the Shell Environment

Extra References
➢ www.tldp.org
➢ www.vmware.com

© October 2, 2005, wiki.novell.com/index.php/Roberts_Quick_References, author of Foundations of Linux networking