Table of Contents Using Unix Systems from Windows
Windows and Unix are different operating systems, with different conventions. Working on Unix systems from a computer running Windows requires the installation and use of tools to connect to the Unix machines.

Logging in to the Unix System

The most basic tool required is a terminal program to log into the Unix system. ITC licenses SecureCRT. Due to security requirements, all the HPC platforms, including the Linux clusters, require the use of ssh2 to log in; this must be selected when you set up your connection to the remote machine. Here is an example of setting up a session to use ssh2 to log in to a cluster called, as an example, Aspen.

It is convenient to give the connection a name, usually the name of the machine to which the connection is made (the default is "New"); it is easy to overlook the topmost field in the "new connection" screen. Of the ITC systems, only blue.unix accepts ssh connections from off-Grounds IP addresses. If you wish to connect to a system such as the Linux clusters from off Grounds, you may either run the UVa Anywhere client, or you can ssh to blue.unix via SecureCRT and then log on to the cluster, e.g.

ssh aspen.itc.virginia.edu
where aspen is again the example name; you would need to substitute the name of the cluster you wish to access.

File Editing

Do not use a standard Windows editor such as Notepad to edit files that will be used on Unix systems. The two systems use different sequences of control characters to mark the end of line (EOL). If you are using the Unix machine from a Windows system, there are a number of options: