Very Computer

Whenever I start a new shell in screen it won't read /etc/profile or
~/.profile.  My xterms are okay, but not even starting the shell on
the command line works I type 'bash -login -i' and I get another
shell, but still .profile isn't read.  If I type "set", among other things,
I get ENV=/etc/ENV.  Any ideas how I might go about tracking the problem?  

Thanks

-Tony

.   .   .   .  . . . . . . . . ._______________________________________.

                               |_____________|___ Southern California _|

I still don't know why "bash -login -i" won't read any of
the profiles but putting everything I need, like aliases,
in /etc/ENV  instead of ~/.profile seems to have done the trick....it now
executes the alias commands in ENV at every shell & subshell
whereas before it didn't because neither ~/.profile nor ~/.bashrc
get read.

I don't think ENV is the normal places for alias's,
Does anyone know if this will cause any problems...

Anyway here's what is in ENV....this may give someone a clue as to
why none of my profiles are being read - some of the symbols here are
cryptic to me:

Quote:># /etc/ENV: Posix conformant startup script for /bin/sh
># We try to emulate the standard shell behaviour: if it is an interactive
># login shell, read /etc/profile first, then ~/.profile.
># A Posix conformant shell will read this file if environment variable ENV
># is set to /etc/ENV (see /etc/ENVIRONMENT).
>#
>case "${--}" in *i*)
>        # Shell is interactive
>        case "${0##*/}" in -*)
>                # Shell is a login shell (-sh)
>                if [ -f "/etc/profile" ]; then
>                        # source /etc/profile
>                        . /etc/profile
>                fi
>                if [ -n "${HOME-}" ] && [ -f "$HOME/.profile" ]; then
>                        # source ~/.profile
>                        . "$HOME/.profile"
>                fi
>        ;; esac
>;; esac

-Tony