To Install Enlightenment/Gnome Desktop

• If you are a new user, this will be automatically the configuration setup for you, containing the enhanced desktop. If you are an old user wishing to update your setup, type

  Eolduser YOUR_LOGIN_NAME

  where YOUR_LOGIN_NAME is the name you use to log into the system.

  Your previous setup information will be saved in a file .clutter_NO where _NO is a randomly generated number.

Starting the Window System

• The xdm package is running on all workstations. This means that you can log in directly at the 'redhat' login screen. If you wish to access the windowing system from the console (for example if you type CNTL-ALT-F2), type

  startx -- :2

  this will run englightenment/gnome. The look is similar to Windows, although with the xfm applications running, you also have the ability to use Apple-like point and drop applications.

  Presently we are running rh7.3 with enlightennment/gnome on many of the machines (you may configure your environement to run with KDE or another widnow manager, if you prefer).

  A more complete description of the options for the window manager using xfm-local is available online.

• To make install the filemanger, xfm-local, you will need to use the package xfm-local_rh.tar.gz which includes the entire package including pixmaps, or the user applications in xfm-apps.tar.gz.

  If you have access to pax, then it is sufficient to type the command

  Exfm-install

  in order to update or install the xfm-apps.tar.gz package.

  If you do not have access to pax, then you need to type

  cd $HOME/.xfm
  rm xfm_local*.tar
  cp /pax/defaults/xfm/xfm-apps.tar.gz .
  gzip -d xfm-apps.tar.gz
  tar -xvf xfm-apps.tar.gz
  ./Install
  cd
  

  This will create the contents of the .xfm directory and create useful xfm resources. To use, exit the windowing system, the changes will take affect on entry to the widowing system. Further information on xfm-local can be found online.

  Be aware that the installation overwrites your existing .zprofile and .xinitrc files (it saves them in a directory names .xfm_SAVE#, where # is a system generated number) Please merge these with the new files if you wish to utilize xfm-local.

---

Installing ssh in your ~./.ssh directory

• To use ssh and scp commands you must install ssh in your home directory. The easiest way to do this is to type

  ssh-keygen

  on your host machine where you have logged in. For example, if you are logged into your account on ocean, type the ssh-keygen command to generate the .ssh directory and to create the file

  ~/.ssh/identity.pub

  Then take the contents of identity.pub, and copy them over to the machine you would like to log into, e.g., pax. You need to the contents of identity.put into a file called

  ~/.ssh/authorized_keys

  in the directory ~/.ssh on pax. You need an entry in this file for each machine that you plan to use to log in to pax. Example Uses of ssh:

  • To log into pax from ocean, on ocean you execute the command

    ssh pax

    This will then log you into your account on pax.

  • To log into a machine with a differnt username, use the -l option on ssh. Thus to log into pax from ocean, assuming your username is different on both machines:
    

    ssh pax -l PAXUSERNAME

  • To copy a file from ocean to pax, do

    scp FILE pax:/pax/USER/.

    where FILE is the file you are copying and USER is your user account. Files can be sent compressed and recursive copies are possible.

  • To execute a command on pax from ocean, use the ssh command with the hostname followed by the command. Thus to list your files on pax from ocean use

    ssh pax ls

  The ssh package can be obtained at from ftp.replay.com. The files are in

  /pub/replay/pub/linux/redhat/i386/

---

Using TeX and LaTeX

• The location of the TeX, LaTeX and AMSTeX files changed. Please delete any references in your .profile, .zprofile, or .csrhc files to TEXINPUTS and TEXFONTS. You can set TEXINPUTS to access local files. Examples are shown in /pax/defaults/profiles/zprofile. The dvips package is no longer putting a4 into the postscript files. there should be no difficulty printing. It is not necessary to use dvips -t letter. This change will affect the position of the document on the page. To test this, try one page using

  dvips -pp 1 FILE

  where FILE.dvi has been processed. Then print FILE.ps.

  It is recommended that you consult the local guide for more information about TeX and LaTeX.

• It is recommended that you use xtem for processing LaTeX and TeX files. Xtem has been loaded into /usr/local/src with binaries in /usr/local/bin.

---

Elf Binaries

• Linux 3.1 uses ELF binaries, not a.out binaries. The installation included libraries which allow old a.out binaries to run, however if you are compiling codes which contain subroutines compiles under a.out and linking them to ELF binaries, there may be difficulties.

---

Using Vi

• The editor vi will now cut and paste from a vi session to a vi session without the shift key needing to be held down. This is because the vi editor now is running vim. The disadvantage of vim is that it creates a local swp file (these can accumulate everywhere). A better way is to request that vim create its swp file in the directory $HOME/tmp (do not use /tmp since then your files are available to everyone). If you install xfm-local_rh you will get this setup done for you. If you wish to install the change yourself, create a file called .vimrc in $HOME, with the contents,

  version 4.0
  :set dir=~/tmp
  

---

Tecplot

• Tecplot version 7 (based on Motif interface) is now running. To run Tecplot, you will need to change your .zprofile to be consistent with the definition of the Tecplot items in the profile/zprofile example file. A complete description of the changes and modifications needed to run the updated version is in /usr/local/src/tecplot/readme.mod. You can run through the demos by using

  /usr/local/src/tecplot/rundemo

USM
inquire@delphi.st.usm.edu
Updated
http://pax.st.usm.edu