Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!ames!oliveb!sun!gorodish!guy
From: guy@gorodish.UUCP
Newsgroups: comp.unix.questions
Subject: Re: Korn Shell
Message-ID: <15368@sun.uucp>
Date: Fri, 20-Mar-87 05:34:44 EST
Article-I.D.: sun.15368
Posted: Fri Mar 20 05:34:44 1987
Date-Received: Sun, 22-Mar-87 23:20:50 EST
References: <580@csun.UUCP> <5680@brl-smoke.ARPA> <2201@ptsfa.UUCP> <772@bobkat.UUCP>
Sender: news@sun.uucp
Lines: 24
Keywords: Korn shell ksh aliases parameters

> Because the overhead on an execve (or whatever under SV)

Just like other things that 4BSD and S5 both inherited from V7, it's
"execve".

> I suppose the shell could figure out when it should pass functions across
> the environment (does SV have something like the `#!interpreter' thing that
> BSD has?);

No, although it *was* Dennis Ritchie's idea originally, so it's not
as if it Wasn't Invented There....  Some vendors that started with
S3/S5 code have added it.

> Doesn't the shell source some file each time it starts up?

Not the Bourne shell.  The C shell will do so, and the Korn shell can
be told to do so, but generally people set up their ".cshrc" or their
Korn shell equivalent (it uses the file whose name is given by the
ENV environment variable) so that it skips most of the setup glop
used for interactive shells when it's running a script.  Saves time -
and, more importantly, saves aggravation; if you use private aliases,
functions, or whatever in your scripts, you'd better either a) not
give those scripts out or b) be prepared for lots of people asking
you why the script doesn't work for them.