Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!cbatt!ihnp4!inuxc!pur-ee!uiucdcs!uxc.cso.uiuc.edu!ccvaxa!wombat
From: wombat@ccvaxa.UUCP
Newsgroups: comp.unix.questions
Subject: RE: BSD & Sys5 Job Control
Message-ID: <29500008@ccvaxa>
Date: Wed, 28-Jan-87 19:34:00 EST
Article-I.D.: ccvaxa.29500008
Posted: Wed Jan 28 19:34:00 1987
Date-Received: Thu, 12-Feb-87 19:01:06 EST
References: <114@dolphy.UUCP>
Lines: 22
Nf-ID: #R:dolphy.UUCP:114:ccvaxa:29500008:000:1143
Nf-From: ccvaxa.UUCP!wombat    Jan 28 18:34:00 1987


/* Written  5:21 pm  Jan 23, 1987 by jpn@teddy.UUCP in ccvaxa:comp.unix.questions */
Both shl and "job control" are unnecessary if you have a true windowing
system.  Both are HACKS to provide capabilities close to window systems
using dumb terminals.
/* End of text from ccvaxa:comp.unix.questions */

Close, but not quite. I used to run a very CPU-intensive process
overnights (specifically, running test suites on a software emulator for
a different machine). Because other people used the same machine for
their heavy computing during the day (more copies of the same emulator),
and because they usually got to work before I did in the morning, I
could get up early, dial up, send the process a SIGSTOP, and *not* get
nasty mail about letting the thing run unwatched during the day. When I
came in to the office, I just sent it a SIGCONT and poked around with
what it had been working on. Try doing *that* with a window system.


"What the hell do you pack anyway, when you're off to see a two-ton
messenger from the stars buried at the end of the world's largest sewer?"
K.W. Jeter, *Dr. Adder*				Wombat
					ihnp4!uiucdcs!ccvaxa!wombat