schemers@vela.acs.oakland.edu (Roland Schemers III) (01/13/91)
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-4323schemers@vela.acs.oakland.edu (Roland Schemers III) (01/13/91)
Thanks to Christos Zoulas for pointing out that the version of tcsh
I had was out-dated. I ftp'd his current version of 5.20.2 and
recompiled the 4.0 versions. We don't have 3.1 running any more, so
the 3.1 versions are still 5-12.
Roland
--
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