How to work offline

Connecting to cochise

Windows users

Windows users may e.g. use putty.exe. Remember to connect via ssh, not via Telnet.

Mac users

Mac users using OS 9 or earlier may access cochise via a program called NiftyTelnet (downloadable from the NiftyTelnet Homepage.). Mac users using Mac OS X has built-in SSH and a terminal application. Just open the terminal, and type ssh username@cochise.uit.no at your prompt (where 'username' is your own user name at cochise).

Linux users

Linux users use the same ssh command as was described for Mac OSX above.

When to work online, when to work offline

As long as you do not have the Xerox tools on your local machine, you must be connected to cochise in order to compile the program, and in order to use it. But you may read the documentation offline, and you may edit the files offline, and thus be able to limit the amount of time you need to be connected to the net. If you work from the university, you might as well stay online.

Reading the documentation offline

When you have your connection up and running, download all the files in the doc directory. Both NiftyTelnet (Mac), putty (Windows) and ssh (MacOSX, Linux) have routines for doing that (see below under Downloading files). Thereafter, you may read them in any web browser (Netscape, Explorer, Opera, ...). Just make sure to open the index.html file first, from that file you will have access to all the other files.

Editing files offline

The best thing to do is to have a good text editor. Do not use Microsoft Word or any other word processor. Word processors and text editors are two different things. Word processors are made to let the text look nice, text editors are made to edit text. In this project, we edit text. Word processors add secret code that makes text nice, but this code only crashes our programs and hampers our work.

Editing files locally on Mac

For OS 9 or earlier, use BBEdit. You may eventually use emacs on the mac as well. We will look into it if the need arises. Note that in Mac OSX you do have emacs installed already.

Editing files locally on Windows

Use emacs on windows. Go to http://ftp.gnu.org/gnu/windows/emacs/21.2/ and download the file emacs-21.2-bin-i386.tar.gz to a folder you may call "emacs" in your program files folder. The file must then be opened with Winzip. If you don't have Winzip, you can find it on http://www.winzip.com. Download the evaluation version, store it in a folder among your program files, and double click on it. Thereafter, go to the emacs folder and ouble click on the emacs-21.2-bin-i386.tar.gz file. You are then presented with a list of filenames in a window. Press ctrl-A (select all) and click on the "extract" symbol. Save the files in the same emacs folder. When you are done, you will find a folder "emacs-21.2" in your emacs folder. Open it, open the bin folder, and drag the "emacs.exe" symbol down to your task bar at the bottom of your screen.

Congratulations! You now have emacs for Windows.

Editing files locally on Linux

Use emacs, just as you do on cochise. Emacs is already installed on all Linux machines.

Downloading files

For downloading files on Windows, see the description on the putty page.

For downloading files on Mac, use Nifty Telnet. Open a new connection with commando-N, then chose commando-S. In order to download files from cochise to your local mac, type commando-2, and thereafter the path and filename you want to copy. Note that you may click on the "copy the content of nested folders" button in order to copy whole directories.

For downloading files on Linux, use the scp procedure. On the command line on your local Linux PC, write (supposing your user name is trond) and you want to copy this file to your local machine and call it off.html:

scp trond@cochise.uit.no:gt/doc/offline.html off.html

In order to copy files to cochise, just switch the arguments.

Troubleshooting

What may go wrong?

I connect via putty or NiftyTelnet, but do not get any "username" prompt
  1. There may be a firewall active. Contact your system administrator
  2. Perhaps you forgot to use SSH instead of Telnet
  3. Perhaps you are not on the internet
More trouble..?
..must be

Last modified: Fri Feb 21 10:51:47 GMT 2003