Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!cs.utexas.edu!yale!ox.com!emv
From: schemers@vela.acs.oakland.edu (Roland Schemers III)
Newsgroups: comp.archives
Subject: [ultrix] tcsh
Keywords: ultrix 4.0 update
Message-ID: <1991Jan12.214223.24589@ox.com>
Date: 12 Jan 91 21:42:23 GMT
References: <4655@vela.acs.oakland.edu>
Sender: emv@ox.com (Edward Vielmetti)
Reply-To: schemers@vela.acs.oakland.edu (Roland Schemers III)
Followup-To: comp.unix.ultrix
Organization: Oakland University, Rochester MI
Lines: 34
Approved: emv@ox.com (Edward Vielmetti)
X-Original-Newsgroups: comp.unix.ultrix

Archive-name: unix/shell/tcsh/1991-01-12
Archive: vela.acs.oakland.edu:/pub/bin/tcsh* [141.210.10.2]
Original-posting-by: schemers@vela.acs.oakland.edu (Roland Schemers III)
Original-subject: tcsh
Reposted-by: emv@ox.com (Edward Vielmetti)

I spoke to soon when I said the binaries I had worked under Ultrix 4.0.
I just switched over to hesiod this weekend, and people who were using the
tcsh started complaining that something was up. 

I traced the problem to the fact that ~ expansion was broke, since tcsh
was compiled under 3.1 the password routines didn't know about hesiod.
After re-compiling tcsh under Ultrix 4.0, it works fine with hesiod.
tcsh under risc Ultrix dumped core the first time I ran it, and 
I traced it down to changing 'char **environ;' to 'extern char **environ'
in sh.func.c. It now runs fine.

I have now created the following in ~ftp/pub/bin@vela.acs.oakland.edu:

tcsh.3.1.mips	tcsh.3.1.vax	tcsh.4.0.mips	tcsh.4.0.vax	tcsh.l

Roland

ps. What was the final status on giving out tcsh binaries? legal? 
illegal? Mine where built form BSD 4.3 sources, and not Ultrix sources.




-- 
Roland J. Schemers III                              Systems/Network Manager
schemers@vela.acs.oakland.edu (Ultrix)              Oakland University 
schemers@argo.acs.oakland.edu (VMS)                 Rochester, MI 48309-4401
~Disclaimer::Disclaimer() { reboot(RB_HALT); }      (313)-370-4323