Path: utzoo!yunexus!gen1!mike
From: mike@gen1.UUCP (Mike CLARKSON)
Newsgroups: comp.unix.xenix
Subject: Re: Requesting info on Xenix
Message-ID: <323@gen1.UUCP>
Date: 1 Jan 88 00:42:13 GMT
Article-I.D.: gen1.323
Posted: Thu Dec 31 19:42:13 1987
References: <461@morgoth.UUCP> <2604@killer.UUCP>
Reply-To: mike@gen1.UUCP (Mike CLARKSON)
Organization: gen1 - York University, Petrie Bldg, Downsview, Ontario CANADA
Lines: 23

In article <2604@killer.UUCP> wnp@killer.UUCP (Wolf Paul) writes:
>
>Well, the BSD v. ATT controversy rears its head again. Stopping and starting
>jobs is a feature of Berkeley UNIX and not supported on most AT&T versions
>(I heard that SV.3 ksh supports it, but nothing prior to that).
>

I hate to jump into anything that would touch off a round of Bsd vs. SysV
flames, but... I've been born and raised on Bsd for a number of years, and
only recently have been using SysV (SCO Xenix 2.2).  Although SysV doesn't
have Berkeley job control, it does have something very nice called shell
layers.  Actually, it's so nice that at this point I'm having trouble 
deciding which one I like better.  Shell layers allow you to run multiple
concurrent jobs, switching back and forth, having them block on output
or just have them all output to the screen.  Needless to say, the interrupt
character to get the shell layer monitor's attention is ^Z.  Note that
this is under SysV.2 not 3, and I find it to be a very good way of managing
concurrent interactive processes.  Bsd types who haven't used shell layers
should look at the Xenix man pages for shl and give them a try.

Mike Clarkson
York University,
utgpu!yunexus!carr!mike