Return to BSD News archive
Newsgroups: comp.os.386bsd.questions
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!yarrina.connect.com.au!news.mira.net.au!news.netspace.net.au!serval.net.wsu.edu!netnews.nwnet.net!oracle.pnl.gov!osi-east2.es.net!lll-winken.llnl.gov!uwm.edu!news.moneng.mei.com!howland.reston.ans.net!ix.netcom.com!netcom.com!kientzle
From: kientzle@netcom.com
Subject: Re: FreeBSD 2.0: tcsh oddity.
Message-ID: <kientzleD2Cr7L.Fy5@netcom.com>
Organization: NETCOM On-line Communication Services (408 261-4700 guest)
References: <kientzleD2B2B7.841@netcom.com> <3f48dr$ado@jabba.cybernetics.net>
Date: Fri, 13 Jan 1995 16:30:57 GMT
Lines: 24
In article <3f48dr$ado@jabba.cybernetics.net>,
James Robinson <james@hermes.cybernetics.net> wrote:
>In article <kientzleD2B2B7.841@netcom.com>, kientzle@netcom.com writes:
>)I installed the tcsh package from the Walnut Creek CD-ROM, and happily
>)set my default shell to /usr/local/bin/tcsh. Which was fine until I
>)started X or invoked Emacs' shell-mode. In either case, I got `csh'
>)in my xterm or shell buffer instead of `tcsh'.
>
>Make sure that you are just starting xterm, and not "xterm -e csh", and that
>there are no strange X Resources infecting your environment. What is your
>$SHELL ?
>
>I have a 2.0R machine that I installed from CD-ROM, using tcsh
>as the shell without any problems.
>
I found my problem. The stock `dot.login' from the CD-ROM, used as
a template for all new accounts, contains the line:
setenv SHELL /bin/csh
Apparently, whoever wrote this forgot that tcsh also reads `.login'
<sigh> Duly fixed here. Thanks for the note that it does work
for someone...
- Tim