Path: utzoo!utgpu!water!watmath!clyde!bellcore!rutgers!ucsd!ames!nrl-cmf!cmcl2!adm!smoke!gwyn
From: gwyn@smoke.ARPA (Doug Gwyn )
Newsgroups: comp.unix.wizards
Subject: Re: weird sh(1) behaviour
Message-ID: <8304@smoke.ARPA>
Date: 3 Aug 88 04:55:01 GMT
References: <163@cstw01.UUCP>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 9

In article <163@cstw01.UUCP> meulenbr@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.