tcsh problem on 2.0.1

[Richard Michael Todd]

ckwang at cs.utexas.edu (Chih-kan Wang) writes:
>I downloaded the compiled tcsh from aux.support.apple.com, put it in /bin,
>edited the /etc/shells, set proper access mode (as the root), and chsh to
>tcsh (in an ordinary user account). Then when I login again and opened
>commandshells, my .login file in home directory didn't get executed. But
>if I changed back to csh, everything went back to normal.  Does anybody
>have any similar experience?

Yeah.  CommandShell won't have the .login or equivalent automatically executed
unless your shell is /bin/sh or /bin/csh.  It checks specifically for those
two shells.  (Hmm--wonder if it works correctly with ksh?)  
The workaround I use is to log in in the "normal Unix" way (the Console 
Emulator), so that all the appropriate setenvs, etc. in .login get executed,
and then start up the Mac environment by hand with the "mac32" or "mac24"
command.  This has the additional advantage that when the MacOS environment
crashes (and sooner or later you *will* find a program that takes it down,
reliability of software for MacOS being what it is...) you don't have to 
re-login again, but can just re-issue the "mac32" command.  

>	tcsh 5.18 compiled for AUX 2.0
I believe the current version is 5.20.  

>p.s. If I have to recompile it, does anybody know where I can find csh
>     source? I got the tcsh source from comp.sources.unix, but it requires
>     csh source too.

Unless you're a University that already has a BSD source licence, you can't.
Such is the joy of AT&T-licenced code.  Pray for a csh rewrite in BSD4.4
that'll be free of AT&T code....
-- 
Richard Todd   rmtodd at chinet.chi.il.us  or  rmtodd at uokmax.ecn.uoknor.edu