1 / 27

“Dilbert” by, Scott Adams, Sep 30, 1994.

“Dilbert” by, Scott Adams, Sep 30, 1994. Basics of the Unix/Linux Environment. Unix Philosophy and Account Information. Unix Philosophy. According to Doug McIlroy Make each program do one thing well.

bond
Télécharger la présentation

“Dilbert” by, Scott Adams, Sep 30, 1994.

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. “Dilbert” by, Scott Adams, Sep 30, 1994.

  2. Basics of the Unix/Linux Environment Unix Philosophy and Account Information

  3. Unix Philosophy According to Doug McIlroy • Make each program do one thing well. • So, to do a new job, build afresh rather than complicate old programs by adding new features (otherwise known as “bells and whistles”). • Machine shop vs. appliance (gives you the tools and you to make appliance)

  4. implications • Typical question from you all: Can UNIX do this? • Typical answer from a professor: NO, but YOU can write a program! Unix enthusiasts think this is the answer the average user wants to hear!

  5. Unix put lots of single minded programs in a row (with pipes “|” ) to do what you need. • Don’t use temporary/intermediate files – use pipe • In other words, Unix prefers to take input from previous program and send output to next program

  6. Write programs that do one thing and do it well. (lean and mean) • Write programs to work together. (pipes)

  7. Accessing unix from Sun lab • Sit down • If the screen is dark – hit any key (the shift key is the “safest” as it does not actually send anything to the computer) or move the mouse to “wake it up”. • Type your CERI/UoM user id (uuid) • Type your CERI unix password *Note that unix machines are case sensitive

  8. The % is the “prompt” from the shell that says it is ready read input. There is also usually a flashing cursor after the prompt. Commands we will enter are shown in italics. <CR> is Carriage Return/Enter. This activity occurs in the terminal window

  9. User ID • User ID: usually a short derivative of your name and the beginning of your email. • Your CERI and UoM user ids are the same User ID’s on the UM system can only be a maximum of 8 characters due to the limitations of early computers. Unix is full of such anachronisms. User ID’s are formed using an algorithm. Take first initial (and maybe middle) and full last name, if that is more than 8 characters, start removing vowels from the back, if still longer than 8 characters, start removing consonants from the back.

  10. User Passwords • Password: a complicated combination of upper and lower case characters, symbols, and numbers that allows access to the account. • Your CERI Unix password is unique to the Sun system • Your UoM Outlook email, Spectrum, Tiger labs, and CERI PC lab password is the same because it is all accessing your primary UoM account. • If you need/use the non-Sun systems (Unix machines in the GPS lab, a faculty member’s Apple, etc.) you will have a unique username/password for each of them.

  11. Passwords • Do not share your password!!!! • Do not leave your password sitting around on a post-it note. • Do not email your password. • If you forget your password, you have to visit the system administrator and (humbly) ask for a new one. There is no way for anyone (except hackers) to figure it out.

  12. Changing your password • Unix passwords can be easily changed using the passwdcommand %passwd for CERI password changes %passwd –rnis Changing password for hdeshon Old password: type in old password New password: type in new password Re-type new password: type in new password again

  13. What not to use for your password: - Your name, address, phone number, or anything that is common knowledge, or can be easily guessed, about you. - Common words. Password guessing programs don’t get tired and can try 1000’s of permutations of passwords based on the above.

  14. What to use for your password: • Something you will not forget. • Mix in numbers and special characters (1, 2, 3 , !, @, #, $, %, etc.). • Should be at least 6 characters long (some systems require longer ones). • (don’t use items from “do not use” list with “1” substituted for “i”, “0” substituted or “o”, etc., the password guessers will try these.)

  15. Accessing unix via SSH • SSH: secure shell login is the preferred way to remotely log on to the CERI unix system; do not use telnet • SSH is secure, easy and with X-tunneling enabled, you can view graphics just as if you were sitting at the remote machine • Machines at CERI accept ssh access from all local Internet providers and other CERI and UoM addresses • If you want access from out of town, you will have to send Bob Debula the IP address of the out-of-Memphis computer

  16. Accessing Suns via SSH Mac or Sun machine 1: open an X11 or Terminal window 2a: mac% ssh -Y hdeshon@enigma.ceri.memphis.edu 2b: sun% ssh -X hdeshon@enigma.ceri.memphis.edu 3: type CERI unix password at prompt PC 1: open the SSH application from the desktop or applications folder 2: enable X11 tunneling via the Settings menu (only do once) 3: click on Quick Connect 4: type in CERI host name and uuid, then password at prompt

  17. Accessing Suns via Exceed • The PCs in the long building have a special terminal emulator program, called Exceed, for remote ssh access to the unix machines. • Once you choose a unix machine via Exceed, the PC screen looks like the unix terminal and regular unix log-in applies • Directions for Exceed setup can be found at • http://www.ceri.memphis.edu/people/mwithers/CERIComputing/Exceed/sshexceed.html

  18. Directories Hierarchical file system which looks like upside down tree Starts at top with “/”, called “root”. Uses “/” to separate directories (known as folders on Apple/Windows) Top Level Directories

  19. Home directories

  20. Up the directory structure or moving backward through the path Down the directory structure or moving forward in the path

  21. Moving around directories • pwd: prints path name of current directory % pwd %/gaia/home/hdeshon [this is what would appear if I had just logged on] • cd: change directory % cd Projects % cdautomatically cd into your home directory % cd ~/bincd into your-home-directory/bin

  22. . and .. • The “.” signifies the current or working directory % cd . No change in location • The “..” signifies the directory directly above you (up) in the directory structure (tree) % cd .. cd back one directory % cd ../../scratch/200GB/hdeshon cd back two directories then forward three into scratch subdirectory hdeshon

  23. Listing directory contents • ls: lists files and subdirectories of the specified path % ls /gaia/home/hdeshon bin srcsuma.new.res % lslist everything in the current directory % ls ~/binlist your-home-directory/bin

  24. Flags & manual pages • Almost all unix commands have a list of flags that can be specified to modify the default behavior % ls –F-F in this case is one flag option for ls • The potential flags are listed within each command’s manual page • To view a manual page, use the man command % man pwd

  25. PWD(1) BSD General Commands Manual PWD(1) NAME pwd -- return working directory name SYNOPSIS pwd [-LP] DESCRIPTION pwd writes the absolute pathname of the current working directory to the standard output. The pwd utility exits 0 on success, and >0 if an error occurs. The following options are available: -L Print the logical path to the current working directory, as defined by the shell in the environment vari- able PWD. -P Print the physical path to the current working directory, with symbolic links in the path resolved. This is the default. STANDARDS The pwd utility is expected to be IEEE Std 1003.2 (``POSIX.2'') compatible. SEE ALSO cd(1), csh(1), getcwd(3) BUGS In csh(1) the command dirs is always faster (although it can give a different answer in the rare case that the current directory or a containing directory was moved after the shell descended into it). 4th Berkeley Distribution November 2, 1998 4th Berkeley Distribution

  26. ls continued % ls -Flist directories with ‘/’ & executables with ‘*’ % ls –alFlist entries beginning with ‘.’ & show in long format -rwx------ 1 hdeshonhdeshon 1201 Jul 10 15:03 .tcshrc* drwx------ 1 hdeshonhdeshon 16384 Aug 1 13:50 bin/ -rw------- 1 hdeshonhdeshon 186668405 Jul 31 2007 suma.new.res From my mac…. %cd /Applications %ls -F Absoft10/ Adobe Acrobat 8 Professional/ Macs have many directories with spaces in the name

  27. Spaces on Unix are somewhat of a problem as Unix does not handle spaces and special characters well because they mean something special in the shell. !@#$%^&*()_+|?><`[]{}\’”:; • The problem with spaces is that the command interpreter of the shell parses (breaks) the command line up into tokens (individual items) based on the spaces. So our file name gets broken into 4 small distinct character strings (“Adobe”, “SVG”, “3.0”, and “Installer”) which causes confusion. • So we have to “protect” the spaces from the interpreter. This is done with quotes. We refer to this file using %ls “Adobe SVG 3.0 Installer” or %ls ‘Adobe SVG 3.0 Installer‘

More Related