Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site codas.ATT.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!mtuxo!mtune!akguc!codas!mikel
From: mikel@codas.ATT.UUCP (Mikel Manitius)
Newsgroups: net.unix
Subject: Re: multiplexing terminals...
Message-ID: <574@codas.ATT.UUCP>
Date: Fri, 20-Jun-86 13:29:51 EDT
Article-I.D.: codas.574
Posted: Fri Jun 20 13:29:51 1986
Date-Received: Sat, 21-Jun-86 11:01:54 EDT
References: <363@hrc63.UUCP> <16600003@ztivax.UUCP>
Organization: AT&T Information Systems, Altamonte Springs, FL
Lines: 16

> "Shell layers" refers to "shl", which is NOT the same as DMD "layers".
> Some people find "shl" useful; it doesn't require any special terminal.
> Its main problem is that it merely multiplexes the terminal for several
> concurrent processes, which have no way to tell what may be visible on
> the current display.  A full window manager solves this problem.

You can very easily tell what is on your screen, if you do "stty loblk".
This blocks processes which try to output to the terminal, if they are
not in the current layer. When the layer becomes current, then they job
is unblocked, and you may get flooded with output.

In my opinion, this is still not as nice as berkeley's job control, but
to get that, you must give up other things....
-- 
			Mikel Manitius @ AT&T-IS Altamonte Springs, FL
			...{seismo!akgua|ihnp4|cbosgd}!codas!mikel.ATT.UUCP