fsu seal Florida State University
Home >> Self Help >> Unix Help >> Unix Environment
 

Computer Science Systems Group
Unix Help

 

Location & Hours
Carothers Rm. 208, MC4530
M-F, 8am-5pm
Map

Contact
send emailhelp@cs.fsu.edu
phone number 850/644-4019
contact us at personnel

 

Setting up Your Default Environment in UNIX


Restoring back to default environment

To restore your dot file back to the defaults that were made when you created the account run the script "GetDefaultDotFiles" located on shell.cs.fsu.edu in /usr/local/bin

Logging in and out:

The following table shows how the login process works for both workstations and xterminals around the department. The example configuration files assume that you are using tcsh rather than csh.

    Workstations (starting an Xserver)
    1) .tcshrc TC-shell configuration file. This file configures your shell environment and should contain configuration information for all shells, such as aliases, prompts, and important environment variables. It is not strictly necessary to put all environment variables here since they will be inherited fromt the login shell, but it is a good idea to put things like your path here so that you know it is always valid when you start a new shell.
    2) .login Login file, but only if the shell is a "login" shell (eg. initial login at console, or when using xterm -ls.) This is where you may want to put special login commands that only execute when you log into a new machine.
    3) .setup Common setup file for both shell and X session logins. I got tired of having my Xterminal and Workstation environments differ simply because I forgot to update one when I made changes so I put common setup commands in this file and reference it from both .login and .xsession.
    4) Applications (Subshells also reference configuration files)
    5) .logout The logout file works simillarly to .login.
    Xterminals (login into previously running Xserver)
    1) .setup Common setup file just like above.
    2) Applications (Subshells also reference configuration files)

Other useful tools to make your computing environment more productive:

    • Gnu ls (gls and dircolors)
      This is the GNU version of ls with color extensions. The easiest way to use it is as follows:
        Make a link for ls to gls somewhere in your private binary directory (I use ~/.bin) and make sure that this is in your path before /usr/bin or /usr/ucb. Note that just making "ls" and alias for "gls" will not work since the dircolors command actually looks for an "ls" binary as part of its setup. For more information take a look at the dircolors man page.

        Then make sure to execute "eval `dircolors -tP`" which will set up the colors based on your .dir_colors file.

        See .tcshrc above for an example.

    • For more information, see the man pages.

    • Midnight Commander (mc) a Norton Commander clone with some very nice features. To use the color features, use "mc -c" in a Color Xterm. Take a look at the man page for more details.

Example emacs configuration files.
.emacs This is a simple function that checks to see if you have modified the configuration file startup.el and byte_compiles it for faster loading.
.lisp/startup.el Main configuration file.
.lisp/nbi-fazy.el Face lock (colorization) file.
.lisp/dark-emacs.Xdefaults Example color defaults for faces.

 

Quick Links

Other Information