These are the computers in the CAL 514 lab and their special roles:
# quiche
# mangue
# otomi
# zapotec
# nahuatl
# tzotzil
User assigned computers:
# yucatec
# lem
# pirx
# polypheme
# zoe
# shannon
Computers in PAR 10 lab:
# hume
# shannon
# bayes
# markov
# gauss
# dirichlet
# xinca - in lab
# copy room printer, called CopyRoom
If you are logging in remotely and then changing your password, please remember to read the directions at the end of this page about logging in remotely, and then do the “ssh quiche” onwards in the paragraph below.
Bring up a terminal (Applications→System Tools→Terminal under Gnome, (KDE Logo)→Utilities→Terminal under KDE), and type “ssh quiche” at the prompt. You’ll have to enter your current password. Once you’ve logged in to quiche, type “passwd” then your current password, then your new password twice (passwd will tell you what to do). Within the hour, your new password will be available on all the machines of the lab.
Make sure you do this every time you leave for the day (or more than an hour or so). Under the Gnome toolbar in the upper-left of the screen, System→Log Out. Under KDE, in the lower-left, (KDE Logo)→Log Out. You will be prompted to click End Current Session.
If you expect to only be away for a little while, feel free to lock your screen. In Gnome, System→Lock Screen; in KDE, (KDE Logo)→Lock Session.
/home
. <your login> .
/groups
/corpora /classes /projects . <your project> .
When you are in the lab, most new users will find JEdit to be the easiest editor for working with text files, such as Python programs or XFST scripts. If you want to use JEdit remotely, you will need to login in remotely using ssh and an X server. If you are using Windows, see the Advanced section below for suggested software to allow you to do this.
Other popular options are Vi and Emacs. They have the advantage that they can be run non-graphically, and thus do not require you to set up an X server. For example, typing “emacs -nw” at the commandline prompt will give you a “no windows” emacs that runs right there in your terminal. (Open another terminal if you wish to continue running commands at the prompt.) This solution works, for example, if you are using Putty to ssh to the lab. Vi and Emacs have the disadvantage that they are not as easy to learn how to use as editors like JEdit; nonetheless, they are very powerful and flexible once you have mastered the basics. Here’s an Emacs tutorial for beginners to get you started. Here is |another tutorial. There may be better ones – search for “emacs tutorial” and you’ll see others.
If you are using a Mac, you might consider using Aquamacs, though plain old Emacs also works quite well.
Printing from Applications
We’ve noticed that some of the programs don’t want to print to xinca (the printer to the right of the door when you first walk in). AbiWord and StarOffice have printed .doc files and kpdf has been working well with .pdf files. I recommend using those. Remember that xinca can print double-sided, and within your application you can tell it to do so. If you prefer to use lpr from the command line, use lpoptions to view the default options and lpq to ensure that the printer is available. If it is not (you receive a “xinca is not ready” message), then follow the instructions in the next section, Printer Snafus.
Printer Snafus
If you find that jobs aren’t printing from a machine, bring up a terminal and type gnome-cups-manager. This application allows you to resume jobs when they end up paused. Simply right click on the printer of your choice and select the mode. Please do not Pause the printer, as this will give you bad karma. If you are logged in remotely and are on a machine with X-windows, then ssh -X and then run gnome-cups-manager.
Replacing Paper
If you find that the printer has run out of paper, feel free to grab a packet from the Hill Library. Please do not load paper that has already been through the printer back into the paper tray. This can cause the printer to jam, suck the paint off your house and give your family a permanent orange afro...
Recycling Paper
Please use the bins in the lab, the hall, or in the Hill Library. Let’s try to keep the paper under control. Thanks!
Remote Logins
One great thing about Linux/Unix is that you can log in from home and run programs. To do this, ssh to tzotzil, then to another machine to do your work. Please don’t run applications and code from tzotzil itself! If you are already on the Linguistics network, you can bypass tzotzil and ssh directly into one of the lab machines from your laptop or from the machines in the Phonetics/Phonology Lab.
If you use some form of Unix (e.g., Linux or FreeBSD), you are all set: just go to a terminal window and type:
> ssh <your_username>@ssh.ling.utexas.edu
Once you have logged in, you should then ssh to one of the other machines, like quiche, mangue, otomi, or coca. For example, once in, you can do:
> ssh otomi
You will need to enter your password both times.
If you have a Mac, you can set up |X11 and do the same stuff as above.
Windows users can use Putty SSH to login in remotely. However, you won’t get X forwarding (the ability to use graphical applications across the SSH connection). Nonetheless, there are some options for getting X forwarding. One possibility is to install Cygwin. Another, perhaps less intensive option is to install Xming, which is free, or Exceed, which is not free. However, do note that the lab caretakers do not support this software and won’t necessarily be able to help you out with any difficulties installing or using it.
X forwarding and remote login
You can run some apps that require a gui by remotely logging in with
> ssh -X <your_username>@ssh.ling.utexas.edu.
The -X option is for X-forwarding.
If you get an error that says any of the following:
please check your disk quota. To do this, run
> quota
Then look at the values under blocks and quota. You need to delete files from your home directory (move them to /scratch, maybe) until the number of blocks you’re using becomes less than the quota.
SSH without Password Prompts If you run ssh from your home machine or laptop, you can set up ssh so that you are not prompted when you ssh into the lab machines. Use the ssh-keygen program to do this, then copy the resulting file to ~/.ssh/authorized_keys
% cd ~/.ssh % ssh-keygen -t rsa
Generating public/private rsa key pair.
Enter file in which to save the key (/home/<your username>/.ssh/id_rsa):
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in id_rsa.
Your public key has been saved in id_rsa.pub.
% cp id_rsa.pub authorized_keys
This will allow you to ssh from any machine in the labs to any other machine in the labs without being prompted for a password. If you want to extend this to your laptop or home machine, copy (or append) an authorized_keys file that you generated from your laptop to your ~/.ssh/authorized_keys file in the lab.