Nasty bug in release 4 Bourne shell

[Guy Harris]

>This exec bug does NOT appear to be in the SPARC version of V.4,
>in either sh or ksh.

So if it was fixed by somebody working on the SPARC version, has that
fix been sent back to AT&T?  The theory is, after all, that V.4 is V.4
is V.4; I wouldn't want to have to choose a processor for my desktop
based on which versions of some bit of processor-independent code got
into the official releases for various processors.

Who is the "keeper" of the various V.4 ports to the "major"
microprocessors?  Does USL keep them all in-house - in which case one
would hope that they would have a *single* source tree for all of them,
with machine-independent code *including* most of the kernel shared
between all processors, or at least that they'd be working on doing so -
or are some of them only in the hands of the organization that did the
port and their customers?