This shows you the differences between two versions of the page.
|
accounts_and_labs:the_linux_network [2010/09/07 09:16] admin |
accounts_and_labs:the_linux_network [2010/09/28 14:20] (current) gerardor |
||
|---|---|---|---|
| Line 5: | Line 5: | ||
| Here you will find the steps to create and access the SCS Linux network | Here you will find the steps to create and access the SCS Linux network | ||
| + | |||
| + | {{:accounts_and_labs:lambda.png|}} | ||
| Line 13: | Line 15: | ||
| * Ubuntu 10.04 Desktop | * Ubuntu 10.04 Desktop | ||
| * has 16 machines on the 'lambda' network (lambda01-16) | * has 16 machines on the 'lambda' network (lambda01-16) | ||
| - | * uses Xming for (X11) connections via the SCS Windows Labs | + | * uses X-Win32 for (X11) connections via the SCS Windows Labs |
| - | * uses [[services:external_access_host_access | access.scs.carleton.ca]] as the external gateway; the machines are not visible from outside of the school's network | + | * uses [[services:external_access_host_access | access.scs.carleton.ca]] as the external gateway; the lambda machines are not visible from outside of the school's network |
| * user home directories are mounted on all 16 lambda's | * user home directories are mounted on all 16 lambda's | ||
| Line 33: | Line 35: | ||
| ==== Logging into the Linux Network ==== | ==== Logging into the Linux Network ==== | ||
| + | |||
| There are two ways to enter the SCS Lambda Linux network: | There are two ways to enter the SCS Lambda Linux network: | ||
| - | - Graphical access via the SCS Windows labs using the Xming application | + | - Connecting to Linux using Windows using an X-emulator (graphical) application |
| - External gateway [[services:external_access_host_access | access.scs.carleton.ca]] (non-graphical) | - External gateway [[services:external_access_host_access | access.scs.carleton.ca]] (non-graphical) | ||
| - | === Xming from the SCS Windows Labs === | + | \\ |
| - | Xming is an X Server that allows you to login to a lambda machine remotely. It's similar to remote desktop in that you get the same login and environment as if you were logged in on the console. | + | === Connecting to Linux using the SCS Windows Lab === |
| - | Once you click on the Xming application you will be logged into a chooser. The chooser displays the lambda hosts that are currently available. When you click a particular lambda host you can then login remotely. | + | The simplest way to log into the SCS Linux network is to log into any SCS lab machine then: |
| + | - click on the 'SCS Linux' desktop icon | ||
| + | - choose a lambda host from the chooser | ||
| + | - login using your SCS Linux account | ||
| + | {{ :accounts_and_labs:chooser.jpg | }} | ||
| + | |||
| + | This will give you full remote desktop style interface using the X-Emulator X-Win32. | ||
| + | |||
| + | |||
| + | == Putty == | ||
| + | |||
| + | Putty is an ssh client that is available free of charge for Windows. With putty you can log into the SCS linux/lambda network. Putty provides a command line/text-only environment (no graphics). | ||
| + | |||
| + | If you use the external access host [[services:external_access_host_access | access.scs.carleton.ca]] as the gateway then you should ''ssh'' to one of the ''lambda''[01..12]s. Note that access.scs.carleton.ca does not have a large variety of programs installed. | ||
| + | |||
| + | If you are in SCS labs you can directly connect to a lambda without logging on to access.scs.carleton.ca | ||
| + | |||
| + | == X-Win32 == | ||
| + | |||
| + | X-Win32 is a Windows X-emulator application. It allows you to launch graphical/X11 linux applications and display them on a Windows machine. X-win32 is installed in the SCS Windows labs ((X-Win32 is a commercial application which means it requires a license)). | ||
| + | |||
| + | The X-Win32 application can be run in many ways, two of them are as follows: | ||
| + | |||
| + | - Run X-Win32 and use putty to launch applications | ||
| + | - Run X-Win32 in XDMCP mode that allows you to login remotely | ||
| + | |||
| + | == X-Win32 and putty == | ||
| + | |||
| + | You can start X-win32 and then use putty-ssh to launch applications from linux. The way you can do this is as follows: | ||
| + | |||
| + | - Log onto the SCS Windows machine | ||
| + | - Launch X-Win32 (All Programs - Xwin32 8.1 - X-Win32) | ||
| + | - Start Putty ssh | ||
| + | - Putty Config: Host Name enter: access.scs.carleton.ca | ||
| + | - Putty Config: Connection Type: ssh | ||
| + | - Putty Config: Category - Connection - SSH - X11 - X11 forwarding - Enable X11 forwarding | ||
| + | - Putty Config: Press OPEN | ||
| + | - login using your SCS login and password | ||
| + | - on the access prompt: ssh -X lambdaXX (where XX is lambda01-16) | ||
| + | |||
| + | |||
| + | Then you can spawn off programs on the putty command line, example: 'xterm &' and they should pop-up on your Windows environment. | ||
| + | |||
| + | == Configuring X-Win32 Manually == | ||
| + | |||
| + | You can run X-Win32 in XDMCP mode that will allow you to login to the lambda machines remotely. This gives you the same environment as if you were sitting in front of the linux terminal, similar to remote desktop under Windows. | ||
| + | |||
| + | <note>The simplest way to connect to the lambda machines is by clicking the desktop icon called 'SCS Linux' on the desktop. This will launch the chooser for you. </note> | ||
| + | |||
| + | You can configure X-Win32 to run a remote linux session as follows: | ||
| + | |||
| + | - Start X-Config: All Programs - X-Win32 8.1 - X-Config | ||
| + | - Press the New Session - 'Manual...' Button | ||
| + | - Connection Method XDMCP- then press Next | ||
| + | - Session Name: lambda | ||
| + | - XDMCP Mode: Indirect | ||
| + | - Host: Choose one of 134.117.27.XXX, where XXX=30,74,75,76,107,109,111,122,129,130,134,135,188,199,200 Example: 134.117.27.111 | ||
| + | - Monitor: 1 (default) | ||
| + | - Then Save | ||
| + | - in the X-Config window click on 'My Session' - lambda and then the Launch button | ||
| + | - Once a connection is made you will get a chooser of lambda hosts, select one and press Connect | ||
| + | - log into the lambda host using your SCS account and password | ||
| + | |||
| + | \\ | ||
| === External gateway: access.scs.carleton.ca === | === External gateway: access.scs.carleton.ca === | ||
| Line 76: | Line 142: | ||
| ==== Remote Host Identification Error ==== | ==== Remote Host Identification Error ==== | ||
| - | If you receive the following error: | + | Do you receive the following error? |
| <code> | <code> | ||
| Line 88: | Line 154: | ||
| 64:1f:1e:50:76:f1:5d:d3:ff:d0:93:4c:e8:73:a9:56. | 64:1f:1e:50:76:f1:5d:d3:ff:d0:93:4c:e8:73:a9:56. | ||
| Please contact your system administrator. | Please contact your system administrator. | ||
| - | Add correct host key in /root/.ssh/known_hosts to get rid of this message. | + | Add correct host key in /home/4user1/hsimpson/.ssh/known_hosts to get rid of this message. |
| - | Offending key in /root/.ssh/known_hosts:21 | + | Offending key in /home/4user1/hsimpson/.ssh/known_hosts:21 |
| RSA host key for lambda01 has changed and you have requested strict checking. | RSA host key for lambda01 has changed and you have requested strict checking. | ||
| Host key verification failed. | Host key verification failed. | ||
| </code> | </code> | ||
| + | |||
| + | This is due to a software and hardware upgrade. What you need to do is ssh to access.scs.carleton.ca and then delete the file ~/.ssh/known_hosts and the ssh key will be re-generated ((You could also edit the known_hosts file and remove the offending key)). | ||
| Line 112: | Line 180: | ||
| If you already have a running process you can //renice// it. ((For more info type //man renice// in a terminal window)) | If you already have a running process you can //renice// it. ((For more info type //man renice// in a terminal window)) | ||
| + | |||
| + | |||
| + | ==== Hardware ==== | ||
| + | |||
| + | Here are some of the specs for the Linux Network hardware: | ||
| + | |||
| + | * lambda01-12: Intel(R) Core(TM)2 CPU 6600 @ 2.40GHz | ||
| + | * lambda13-16: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz | ||
| + | * 4 GB RAM | ||
| + | * lambda13-16: ASUS ENGTX480 videocards | ||
| + | |||
| + | |||
| + | |||