djc@wlcrjs.UUCP (David J. Carpenter) (07/03/85)
How does one really use the /dev/sxt--- devices on an AT&T 3b2 Unix 5.2? There is a progrsm shl, shell layer manager, that lets you have multiple shells all spewing forth at once, but how do you separate the output into windows, for example, at the terminal? Is the device driver in there incapable of this right now? Do you have to write one? (or modify it) The manual makes little mention of this. Thanks... ..!ihnp4!wlcrjs!djc
mcferrin@inuxc.UUCP (P McFerrin) (07/04/85)
> How does one really use the /dev/sxt--- devices on an AT&T 3b2 Unix 5.2? > There is a progrsm shl, shell layer manager, that lets you have multiple > shells all spewing forth at once, but how do you separate the output into > windows, for example, at the terminal? Is the device driver in there > incapable of this right now? Do you have to write one? (or modify it) > The manual makes little mention of this. > > Thanks... ..!ihnp4!wlcrjs!djc The output can not be separated. However, there is a shl command to cause the output to be blocked to your terminal when you leave that layer (e.g. switch to another layer). A shl status command is available to inquire about the status of other running layers which will indicate if it is blocked on output. If you really want multiple windows, there is the DMD layers software which might not be available for the 3b2.
robert@gitpyr.UUCP (Robert Viduya) (07/05/85)
> > How does one really use the /dev/sxt--- devices on an AT&T 3b2 Unix 5.2? > > There is a progrsm shl, shell layer manager, that lets you have multiple > > shells all spewing forth at once, but how do you separate the output into > > windows, for example, at the terminal? Is the device driver in there > > incapable of this right now? Do you have to write one? (or modify it) > > The manual makes little mention of this. > > > > If you really want multiple windows, there is the DMD layers software > which might not be available for the 3b2. The DMD layers software is available for the 3B2. The software handles all the output seperation by wrapping all data sent from and to the terminal in a multiplexing type protocol. The DMD terminal, unlike most other terminals, is smart enough to handle this. robert -- Robert Viduya 01111000 Georgia Institute of Technology ...!{akgua,allegra,amd,hplabs,ihnp4,masscomp,ut-ngp}!gatech!gitpyr!robert ...!{rlgvax,sb1,uf-cgrl,unmvax,ut-sally}!gatech!gitpyr!robert
fred@mot.UUCP (Fred Christiansen) (07/10/85)
[]
the shell layers offered by shl(1) normally multiplex their output to
your terminal. however, there are shl(1) commands to specifically
block/unblock output from specific layers.
i am not aware of any connection between this facility and
the windows in the Unix PC or the DMD. in fact, i am lead to understand
that each is different from the other two.
--
<< Generic disclaimer >>
Fred Christiansen ("Canajun, eh?") @ Motorola Microsystems, Tempe, AZ
ihnp4!{attunix, btlunix, drivax, sftig, ut-sally!oakhill}!mot!fred
trwrb!{flkvax, wlbr}!mot!fred OR oakhill!mot!fred@ut-sally.ARPA