On Wed, Mar 28, 2001 at 08:40:21AM -0500, Jeffry Smith
<[EMAIL PROTECTED]> wrote:
> > Maybe. Some U*ixes don't let you change your own shell. You may need
> > to get the system administrator to change it for you.
>
> or just have a "sh" command run on start-up.
Indeed, this is what I do here at work. Some of our machines have
bash installed, but Tru64 won't let you change your shell to something
not in the /etc/shells file. Since bash isn't on all machines, I
wouldn't want to set it as my shell, as that would mean that I couldn't
log onto some machines.
Instead, I have ksh (a decent shell for programming, but bash
interacts more nicely) as by default shell. When I log in, my .profile
checks a file to see if this host is in the list of hosts that can run
bash (because it's NFS automounted, it's available on some machines on
which it won't execute). If the current host can run bash, I then find
where it is installed. If that succeeds, I then run bash with
'--login'.
I used to 'exec' bash, but occassionally ran into problem where if
bash failed to start properly, I wouldn't be able to log in at all.
Instead, I run bash from my login shell (ksh). I have a one line
.bash_logout file which reads 'exit 0'. My login shell (ksh) checks the
return from bash. As long as it is 0, it knows bash was able to run
successfully, and exits the login shell when bash exits.
This has worked like a charm so far...
--
Bob Bell Compaq Computer Corporation
Software Engineer 110 Spit Brook Rd - ZKO3-3/U14
TruCluster Group Nashua, NH 03062-2698
[EMAIL PROTECTED] 603-884-0595
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
