What is Setup?

The SEP standard setup is an attempt to simplify the maintenance of your login and X Window system environment. In the past, people would get started at SEP by copying a bunch of setup files from another user. Problems would arise when your copy got out of date. You'd need to get a new copy from someone else, but if there were some customizations that you had made, these would be lost. If you asked someone for help, they wouldn't know where to begin because your setup was completely different from everyone else's. It was a big mess. To fix the problem, the SEP setup was created.

The SEP setup provides a basic setup that works on all SEP machines, with all window systems, and that allows users to customize their setup without causing compatibility problems.

What does Setup do?

When you get a new account, the global setup just puts a few files in your home directory. These are files that you shouldn't change. The files are:

  1. .login → this contains instructions for when you login, telnet, or rlogin to an account
  2. .logout → contains instructions for when you logout
  3. .cshrc → first file accessed by the shell when you run csh or tcsh
  4. .xinitrc,.X11Startup,.xsession → contains instructions for when you begin an xsession
  5. .Xdefaults → defaults for X11 applications (such as colors, placement, etc.). This file can be copied from $SETUP/skel/ and modified.
  6. .vueprofile → first file checked when you login on an HP console
  7. .rhosts → contains a list of “safe” hosts. Be careful if you add any hosts here, it could create a security hole.
  8. .datapath → used by SEPlib to determine where to put scratch files. It's usually set to something intelligent, but you can change it if you wish.

You will also have a directory called Setup in your home directory where you can put your customization files.

What can I customize?

There are essentially two environments you can modify: your shell environment and your X-windows environment.

Shell customizations

  1. cshrc.generic → contains your personal environmental variables, additions to your path, other variables
  2. cshrc.[type] → (type=sgi,linux,sun,ibm,hp,i586,etc) same as cshrc.generic but will only be used when you are on the specified platform
  3. alias.generic → list of your personal aliases for csh and tcsh
  4. alias.[type] → platform-specific aliases
  5. login → personal instructions when logging in
  6. login.[hostname] → personal instructions when logging in on a specific machine

X-window customizations

  1. windowmanager → contains your preferred windowmanager and the rc configuration file (if required). A good place to look for a new windowmanager is the Window Managers page.
  2. tvtwmrc → if you don't have a windowmanager file, you can use this to change the appearance of your windows environment (pull-down menus, color scheme, etc)
  3. Xres.screen1 → change default screen fonts
  4. Xres.[type] → Xdefaults for specific platforms
  5. clients.clock → change your on-screen clock
  6. clients.remote, clients.extra → to add additional windows such as extra xterms,xload, xbiff,etc.

Changing/setting paths

  1. Override your personal device settings with:set mypath=/net/koko/[username]/bin/[type]:/net/koko/[username]/bin/all:in either cshrc.generic or cshrc.[type]. Note that you must have the colon at the end of the command.
  2. Add additional paths with:set pathextras=/my/additional/paths:also in cshrc.generic or cshrc.[type], also requires the ending colon.


An email from Bob about how to play with ssh.

sep/internal/setup.txt · Last modified: 2015/05/27 02:06 (external edit)
CC Attribution-Share Alike 4.0 International
Driven by DokuWiki Recent changes RSS feed Valid CSS Valid XHTML 1.0