Please browse through the UNIX manual section 1 for an introduction to the system. You can find a copy in room 5 of Bradley Hall. You should especially see the manual pages for the program called 'csh'. The easiest way to see the manuals is to use your computer terminal - the 'man' command (don't type the ' ' ) is an online version of the manual - it is guaranteed to be the most up to date version available. the command 'man -k something' lists all the references to the subject 'something'. If you know the subject or command name you can say 'man subject', as in 'man csh', or even 'man man'. In fact, you should definitely try 'man man' if you haven't tried it yet! Changing Your Password: You should use the command 'yppasswd' , rather than 'passwd', to change your password. This command is necessary because all Suns within our domain share a common data base for passwords. This data base is kept on one Sun. Therefore in order to change your password globally you must change the passwd that is kept in that data base. Note that there are a few other system information which are kept in a global data base. For more information you should consult the man pages for ypcat(1), ypfiles(5) and ypwhich(8). You should choose a password which is hard to guess - not your name or your dog's name. There are programs which try to break into systems by guessing passwords - they try every word in the dictionary, all the football teams, etc. The best way to foil that is to put random caPitals or nu4mbers into your pAsAwOrD! I check from time to time! Sun Machines: Because of NFS (the Network File System) it doesn't matter which Sun you log on to, you will always access the same files. The only exception are files in the directories /usr/tmp, /usr/spool and /tmp. These files are private to each machine. Other Machines: You can also get accounts on the vax running UNIX, named eleazar (or u2 for short) by going to kiewit and asking the consultants. You have an account on the non UNIX machine D1, which has a user id of your college id, and a password which may be the first three letters of your last name. You should forward your mail from D1 to the Suns. There are also many IBM RT's running UNIX - you can get an account on them by logging in as newuser and doing what the program says. Your acount will be set up within a day or two. Reading Your Mail: You can read mail from any Sun - it is all stored in the same place. In your .forward file you can specify a place to forward your mail to. You should go to all machines that you have accounts on, and direct the mail to one particular system (remembering that all Sun mail goes to the same place! You should do this on D1 as well, or on the Macintosh Blitzmail. Printing: Although there are no printers directly connected to the Suns you can print on machines connected to other systems. There is a Xerox printer in room 5 which you can print to by setting your PRINTER environment variable to Bradley_005 or by using the command lpr -PBradley_005. This printer is also known as Dartps1, and prints tex, troff, and plain files. It does not print postscript. Print jobs to Bradley_005 are spooled through the vaxen U0 (Dartmouth.edu) and U2 (Eleazar), so those machines must be up for it to run. There is also a print command, < maha >, which bypasses U0 and gives you more printing options. You can < man maha > to find out more. There are apple ntx laserwriters in room 316. They are called bntx and b316, and print tex, troff, postscript, and plain text. Jobs for these printers are processed on the Suns, and then sent to the appletalk network and to the printer. You will get mail if a printing error occurs - usually the printer is not turned on. Say lpr -Pbntx. Ther are also some apple laserwriters which don't have the capabilities of the ntx, and print jobs to them are processed on U0 and then sent to the honeywell D1 and out to the appletalk network. Because they go through so many other machines, and because some of these machines are small and overloaded, you print job may not come out the other end quickly, or at all. If you decide to abort a job sent to these machines you must use the pristat and priabort commands. Examples of these machines are martiniwriter, RamanujanWriter (aka logicwriter), northstarps3 (aka nps3), bradley_003, and kiewit_public. You can print to bradley_003 directly from the suns by printing to b3 - the printer is the same, but the path is different! If you look at the file /etc/printcap you will see a list of the names of the printers that you can print to, and their aliases. In several cases different paths to the same printer are specified by different names, and some of the names are similar. For example, a tex job submitted to b316NTX may well look different than one submitted to b316ntx!!! There is an IBM pageprinter in room 105 Bradley, named b105 (rpp4) which prints plain text and troff, but not postscript or tex. If you want old fashioned high speed printer output print to lp. You output can be picked up at the window in Kiewit. Using the Windows System: The window systems is controlled by the program 'suntools(1).' To enter the window system simply issue the command 'suntools'. You have been given a simple startup file called ~/.suntools which will create two windows for you. See the manual pages on suntools to learn about setting a default configuration. You should note that suntools can not be run remotely. That is, you cannot access suntools running on a machine other than the one you are using. This fact is also true for any graphics programs which you might want to run. They will only affect to screen of the Sun which is running the programs. As a result, it is not a good idea to put the suntools command in your .login file unless you plan to use only one workstation. You can also use X windows on the Suns instead of suntools. You need some configuration files to get started, for example .Xdefaults, and .awmrc. If you have questions, feel free to ask, as X is a bit harder to get started on, though some of us feel that it is much nicer in the long run. You can run X remotely! Usually the command xinit starts X windows. The command X by itself if often aliased to "xinit; fixkeys", and you can check this by typing . (fixkeys recovers control of your keyboard if you crash in X) Groups: You can find out which groups you're in by issue the command 'groups'. Your default group should be the first group name returned by the 'groups' command. You might also realize that your login directory is within a directory named after your default group. Note that it is possible that you are not only one in your default group therefore you should take more care when setting your umask. Hosts: Currently the Suns distrust machines which are not a Sun. This means that rcp will not work from any of the other UNIX boxes on campus to a Sun. You can create a .rhosts file for machines you trust. Note that if you trust a machine you will not be prompted for a password when you log in from that machine remotely. Lost Files: Backup is run every day at 15:00 except Saturday and Sunday. If you lose a file it can probably be retrieved if it was created before the last backup. Xerox's: If you want or need an account on the Xerox workstations, see Wayne. The Xerox's are completely seperate from the Suns, and do not run UNIX. Differences: There are many site specific differences between UNIX systems, and many of the things that you may have taken for granted at another site may have been local custom commands and systems which are not the same here. This is especially true for printers. If you type 'help', or 'man help', you will get a somewhat up to date listing of these differences. Things are always changing! Local commands and systems: Local commands, and many-well known command that aren't actually supplied by Sun live in /usr/local/bin. You could list that directory to see them all. They all should have man pages (but a few might not.) Here are a few: troff - use ditroff, for questions and problems contact me (wbc) tex - contact Sam Bent, for printing and X previewers contact me. prtex - a way to print tex files latex - bibtex - for bibliographies dviview - a tex (dvi) previewer for sunview - see Sam xdvi, texx - tex previewers for X windows - see me xfig and fig - interactive graphics which can be used in tex documents via transfig calc -- an infinite precision arithmetic calculator -- see Jeff Shallit ( ~shallit/Calc/calc ) PARI -- a calculator system for number theory -- see Jeff Shallit ( ~shallit/PARI2/pari-1.32/gp ) maple -- available on U2 (eleazar) but not on the Suns mh and x mh - mail readers elm - another mail reader emacs - gnu emacs - the most complete editor. To learn it type 'emacs', then control-h (for help) and do what it tells you till you get to the online tutorial. gcc - the gnu project c compiler - better than Sun's! gdb - the gnu project's debugger perl - a substitute for awk nawk - the new awk X11 - see /usr/bin/X11, where the programs are. webster - an online dictionary - see Jeff Shallit apl - see Jeff kcl - kyoto common lisp - see me prolog - a version of c prolog precisionlib - a high precision library sc - a spreadsheet program - if you use this a lot,see me macsyma - you can only run this on killington! maha - to print on the xerox printer in room 5 nslookup - to get the numerical address of a machine so you can ftp or telnet to it spider - ask Sam Bent priabort and pristat - to abort jobs sent to postscript printers sas - statistical analysis package rcs - revision control system style - analyses your writing style tgrind and vgrind - format c programs sd2ip - print a screendump - Sam fixkeys - run this (from another terminal) when you console locks up! redact - an editor when you log in from your Mac Source: We don't have source to Sun supplied software, but source to other software is in /toe/src/local/bin, /toe/src/misc/GNU, /new/X11R4, /toe/src/misc/X11R3, and /toe/othersrc/misc. Problems & Comments: If you should have any problems, comments or suggestions please feel free to send mail to manager (wbc). Your message will get to people who can make changes to system. If for example, any of this document is unclear or incorrect, don't hesitate to send mail describing the problem. If you think there is a bug, pleas try to be specific and complete in describing it. Tell me the input files, the exact command line used, and details about what goes wrong. -- Wayne Cripps (current manager)