From: gleasokr@rintintin.Colorado.EDU (Kris Gleason) Subject: tcsh 6.03 -- to patch or not to patch? Date: Thu, 28 Jan 1993 01:16:45 GMT
I got the latest-and-greatest tcsh binaries, linked with libc.so.4.2
from sunsite.unc.edu. As you might have guessed, it was a big problem when I
installed it... had problems with pipes (rusty pipes). Basically, at
seemingly random times, commands executed through a pipe would either
stop running early (only fixed by ^C), or kill the shell (the shell caught
user signal 2 and exited).
So, I got the source, applied the included diffs, recompiled with all new
stuff, and got identical results. I looked at the diff file, and could make
very little sense out of what was happening with SIGUSR2, if anything.
Finally, I recompiled again, this time without the diff. The compile went
smoothly, and the new binary has had no problems with any pipes. In fact,
it has no problems that I have noticed at all.
So, if you're still with me... I was just wondering why the original source
was changed in the first place. Was this necessary for an earlier kernel/gcc
configuration? (currently at 0.99.1, gcc2.3.3.. about to compile 0.99.4)
Is there some other problem that I have not noticed in everyday use?
Thanks.
Kris