to job control or not to job control (was UNIX Futures)

[dave at garfield.UUCP]

In article <198 at desint.UUCP> geoff at desint.UUCP (Geoff Kuenning) writes:
| Stopping a job is a scheduling decision, nothing more.

Not at all. It is informing the process that it's enviroment
is going to change - the screen is going to be messed up. Processes
which don't care about the screen state can ignore it, processes
that do can do something about it. Same with SIGWINCH.

dave
-- 
The             UUCP: {utcsri,ihnp4,allegra,mcvax}!garfield!dave
Mercenary     CDNNET: David Janes <dave at garfield.mun.cdn>
Programmer    "There can only be one!"