Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!nbires!hao!hplabs!cae780!amdcad!sun!gorodish!guy
From: guy%gorodish@Sun.COM (Guy Harris)
Newsgroups: comp.unix.questions
Subject: Re: BSD & Sys5 Job Control
Message-ID: <11888@sun.uucp>
Date: Thu, 22-Jan-87 14:07:02 EST
Article-I.D.: sun.11888
Posted: Thu Jan 22 14:07:02 1987
Date-Received: Fri, 23-Jan-87 20:39:06 EST
References: <1324@cadovax.UUCP> <161@piaget.UUCP> <114@dolphy.UUCP>
Sender: news@sun.uucp
Lines: 19
Summary: In BSD job control, *some* processes must be changed to properly handle job control; most UNIX commands don't notice.

> In BSD, processes must be coded to properly handle job control.

In job control, programs that *want to know* about job control, or that have
sections where they don't want to be stoppable, must be changed to know
about job control.  Most UNIX utilities don't know about it.

In shell layers, programs that want to know that the terminal has been taken
away from them have no way of finding this out.  Thus, if they have to reset
some mode in the terminal (not in the terminal driver, but in the terminal
itself - e.g., turning off Tektronix mode on a VT100 with a Tektronix
emulation board) can't be told when to do so.

> Sys5's sh & korn-sh (at least ours) doesn't know about job control

That's because vanilla System V doesn't *have* job control.  "ksh" will
support job control on systems which have it.  In fact, I've seen code in
"ksh" that looks like it tries to use the shell layers kernel support to
implement something sort of like job control, if you have shell layers
kernel support but not job control.