Path: utzoo!mnetor!uunet!husc6!mailrus!nrl-cmf!cmcl2!brl-adm!brl-smoke!gwyn
From: gwyn@brl-smoke.ARPA (Doug Gwyn )
Newsgroups: comp.unix.wizards
Subject: Re: SVR3.0 vs BSD4.3
Message-ID: <7551@brl-smoke.ARPA>
Date: 25 Mar 88 22:33:08 GMT
References: <12414@brl-adm.ARPA> <4361@megaron.arizona.edu> <7499@brl-smoke.ARPA> <7514@brl-smoke.ARPA> <2050@munnari.oz> <7542@brl-smoke.ARPA> <2038@epimass.EPI.COM>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 13

In article <2038@epimass.EPI.COM> jbuck@epimass.EPI.COM (Joe Buck) writes:
>Correct me if I'm wrong, Doug, but I thought in shl you can't stop a
>process that isn't producing terminal output, ...

I believe that's correct, due to having the sxt terminal multiplexor
doing the actual work.

I didn't say "shl" was exactly the same or even as useful as BSD-style
job control, just that it was the nearest AT&T UNIX equivalent.  I
suspect you'll see BSD-style (signal-driven) job control in some
future AT&T UNIX, especially given the AT&T/Sun merged-UNIX project.

Commercial UNIX continues to accrete features...