| 1 | = Terminals and Shells = |
| 2 | |
| 3 | [[Image(univac_1965_2.jpg, center)]] |
| 4 | ''Taken from UNIVAC promotional materials circa 1960'' |
| 5 | |
| 6 | The terminal has been the primary means of interfacing with a cluster computing machine since the 1960s. Today, users who are working on a laptop or desktop with an operating system that is based on Unix will have a useful terminal built into their operating system. This includes anyone using Mac os X or any flavor of Linux. |
| 7 | |
| 8 | == Mac Terminal == |
| 9 | |
| 10 | To access the terminal program on a Mac go to |
| 11 | |
| 12 | ''Applications -> Utilities -> Terminal'' |
| 13 | |
| 14 | [[Image(utilities_terminal.png, center)]] |
| 15 | |
| 16 | This will launch a terminal containing a unix shell. The unix shell is a command line interpreter which both allows you to pass commands to the operating system and displays output. Currently, the default shell for most unix based systems is the Bourne Again SHell or bash shell. Your shell can be modified to provide a custom environment and we will go into detail on how to make these modifications in later sessions. |
| 17 | |
| 18 | [[Image(terminal.png, center)]] |
| 19 | |
| 20 | == Ubuntu Terminal == |
| 21 | |
| 22 | In Unity versions of Ubuntu (11.04 and later) the easiest way to access the terminal is through the search function of the dash |
| 23 | |
| 24 | ''Dash -> Search for Terminal'' |
| 25 | |
| 26 | [[Image(ubuntu_terminal.png,center, 80%)]] |
| 27 | |
| 28 | [[Image(terminal2.png, center)]] |
| 29 | |
| 30 | == Windows "Terminal" == |
| 31 | As Windows is NOT a Unix based OS, it lacks a native terminal emulator that is capable of provide a Unix shell. This will require a work around. For our requirements, the most common solution is the installation of an open source terminal emulator called PuTTY that supports the communication protocols discussed below. If you are using a Windows machine and you have not already downloaded PuTTY you should do so now. |
| 32 | |
| 33 | [[http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html|Download Putty]] |
| 34 | |
| 35 | [[http://the.earth.li/~sgtatham/putty/0.62/htmldoc/|Putty Manual]] |
| 36 | |
| 37 | After you've downloaded the PuTTY.exe file, move it to the location you prefer and double click to launch. |
| 38 | |
| 39 | [[Image(PuTTY_launch.png, center)]] |
| 40 | |
| 41 | To log onto cypress, enter cypress1.tulane.edu (or cypress2.tulane.edu) into the Host Name field and make sure the port is set to 22. Click on Open and you will be given a login window to cypress. |
| 42 | |
| 43 | [[Image(PuTTY.png, center)]] |
| 44 | = Remote Access = |
| 45 | |
| 46 | == A short History == |
| 47 | Scientists have been performing computations remotely since 1940 when George Stibitz used a Teletype machine to perform remote computations on a Complex Number Machine in New York City from the an AMS conference held at Dartmouth (http://history-computer.com/Internet/Dreamers/Stibitz.html). By 1973, standards were defined for a set of remote access protocols called Telnet which are still in use today. Subsequently (1983), the Berkley Software Distribution (BSD) Unix operating system instituted an alternative protocol called Remote SHell, or rsh. While still available on most systems, rsh is not recommended for common use as it lacks encryption. In 1995, this lack of security lead a researcher named Tatu Ylonen to invent a secure set of protocols after his University was the victim of a sniffing attack. He named his protocols Secure SHell, or ssh, and this has become the default means of remote access for unix based machines world wide. |
| 48 | |
| 49 | |
| 50 | |
| 51 | == Secure SHell (SSH) == |
| 52 | === Linux and Mac === |
| 53 | Users on Mac and Linux workstations have ssh available on the command line. |
| 54 | To connect to a remote server run the following: |
| 55 | |
| 56 | {{{ |
| 57 | user@localhost> ssh remoteusername@remotehost.example.com |
| 58 | }}} |
| 59 | |
| 60 | The first time you log into a new machine, you will be asked if you trust the server. For instance, the first time you log into Cypress using PuTTY you will receive the following prompt: |
| 61 | |
| 62 | [[Image(host_key.png)]][[Image(host_key_mac.png, 500px)]] |
| 63 | |
| 64 | Click on yes (or if using !Mac/Linux terminal simply type "yes" at the corresponding prompt). You should now be prompted for the password associated with your remote username. |
| 65 | |
| 66 | For those who have accounts on Cypress, you can connect to cypress by running the command |
| 67 | |
| 68 | {{{ |
| 69 | user@localhost> ssh tulaneID@cypress1.tulane.edu |
| 70 | }}} |
| 71 | |
| 72 | and entering the password associated with your tulaneID across Tulane resources. If you are using one of our temporary accounts for the workshop you will use the alphanumeric user id and password provided. |
| 73 | |
| 74 | == CHECKPOINT == |
| 75 | Everyone should now have a terminal open and be logged into Cypress. If you are not logged on to Cypress, please raise your hand and someone will assist you. |
| 76 | |
| 77 | We will return to SSH shortly, but first we need to discuss [[cypress/BasicLinuxComands|Basic Linux Commands]]. |
| 78 | |
| 79 | == Tunneling X Windows Session via SSH == |
| 80 | === Linux and Mac === |
| 81 | Users on Mac and Linux workstations have ssh available on the command line. |
| 82 | |
| 83 | To connect to a remote server with X window tunneling run the following: |
| 84 | |
| 85 | {{{ |
| 86 | user@localhost> ssh -Y remoteusername@remotehost.example.com |
| 87 | }}} |
| 88 | |
| 89 | === Windows === |
| 90 | Windows users will need to download an X window server/client software. |
| 91 | |
| 92 | [[http://www.straightrunning.com/XmingNotes/|Xming]] |
| 93 | |
| 94 | [[http://www.cygwin.com/|Cygwin]] |
| 95 | |
| 96 | [[cypress/BasicLinuxComands|Next Section: Linux Commands]] |