Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!uwvax!oddjob!mimsy!aplcen!osiris!phil
From: phil@osiris.UUCP (Philip Kos)
Newsgroups: comp.sys.m6809
Subject: Re: Remote terminal in Level II
Message-ID: <1268@osiris.UUCP>
Date: Tue, 7-Jul-87 13:26:10 EDT
Article-I.D.: osiris.1268
Posted: Tue Jul  7 13:26:10 1987
Date-Received: Fri, 10-Jul-87 06:11:53 EDT
References:  <1789@ihwpt.ATT.COM>
Organization: Johns Hopkins Hospital
Lines: 31
Summary: shell, not UN*X

In article <1789@ihwpt.ATT.COM>, knudsen@ihwpt.ATT.COM (mike knudsen) writes:
> I believe this is yet another limitation of the way OS9 executes
> shell script files.  Your bootup shell creates a sub-shell to
> run the startup file....
> 
> UN*X fortunately has a special '.' operator that means
> "don't run this in a subshell; do it exactly as if I were
> typing it on /TERM."...

Actually, Mike, this is a shell command and not a UN*X operator.  It's even
a different built-in in different shells (csh, for example, maps it to the
verb "source").  "Running" a shell script, i.e. starting up a text file as
a process, is *always* handled by UN*X by starting the named (or default)
"shell" with the text as stdin.  Anything else has to be done by the shell
itself.

If the bootup shell were hacked to do things like this, the procedure
could probably be changed so that this was possible.  I'm not really fami-
liar with OS9 so I can't say if this is really possible or not; I mainly
wanted to correct a mis-impression of UN*X and thereby suggest a solution.

> -- 
> Mike J Knudsen    ...ihnp4!ihwpt!knudsen  Bell Labs(AT&T)
>     Delphi: RAGTIMER    CIS: 
> 		"Just say NO to MS-DOS!"

...!decvax!decuac!\                                               Phil Kos
  ...!seismo!mimsy!aplcen!osiris!phil           The Johns Hopkins Hospital
...!allegra!/                                                Baltimore, MD

"The all-weather breakfast." - F. Theater