weird sh(1) behaviour

[Doug Gwyn]

In article <163 at cstw01.UUCP> meulenbr at cst.UUCP () writes:
>sh file
>and
>sh <file
>are NOT equivalent.

That's for sure.  I had a heck of a time getting both these
invocations to not source the user's $ENV file while still
having the normal interactive sh do so, in our extended sh.