Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!philabs!cmcl2!harvard!talcott!panda!genrad!decvax!decwrl!pyramid!hplabs!sdcrdcf!ism780c!tim
From: tim@ism780c.UUCP (Tim Smith)
Newsgroups: net.unix-wizards
Subject: Re: UNIX Futures
Message-ID: <1413@ism780c.UUCP>
Date: Tue, 8-Apr-86 17:09:28 EST
Article-I.D.: ism780c.1413
Posted: Tue Apr  8 17:09:28 1986
Date-Received: Mon, 14-Apr-86 02:08:16 EST
References: <67@cstvax.UUCP> <2864@amdahl.UUCP> <137@myab.UUCP> <6534@utzoo.UUCP> <1524@wucs.UUCP> <2417@teddy.UUCP>
Reply-To: tim@ism780c.UUCP (Tim Smith)
Organization: Interactive Systems Corp., Santa Monica, CA
Lines: 24

In article <2417@teddy.UUCP> jpn@teddy.UUCP (John P. Nelson) writes:

> I sure wish people would read before flaming.

I sure wish people who lived in glass houses ... :-)

>  The original article was talking about SHELL LAYERS "shl" which
> is a System V poor imitation of Berkeley job control.

Shell layers is not an attempt to imitate job control!  Shell layers
is an attempt to solve the problem of multiplexing input to several
processes.  Job control seems to be a kludge attempting to solve
multiple problems ( process control, input multiplexing, and output
multiplexing ) all at once.

> Under Shell Layers, a ^Z (or equivalent keystroke) passes the
> terminal input to a different program, but the program that was
> intercepted is not told, and is NOT EVEN STOPPED (output will
> continue).

Shell layers may be set up so that any process that attempts to do IO
will block.  Output in this case will not continue.
-- 
Tim Smith       sdcrdcf!ism780c!tim || ima!ism780!tim || ihnp4!cithep!tim