Xref: utzoo comp.unix.wizards:26207 comp.bugs.4bsd:1839
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!qt.cs.utexas.edu!zaphod.mps.ohio-state.edu!sdd.hp.com!decwrl!mejac!orchard.la.locus.com!turnkey!itcorp!geoff
From: geoff@ITcorp.com (Geoff Kuenning)
Newsgroups: comp.unix.wizards,comp.bugs.4bsd
Subject: Re: How to mess up your tty: (sleep 3;vi)&;vi\n<wait 5 seconds>ZZfg\n
Message-ID: <1991Jun29.084246.29248@ITcorp.com>
Date: 29 Jun 91 08:42:46 GMT
References: <2997.Jun2704.59.0991@kramden.acf.nyu.edu>
Followup-To: comp.unix.wizards
Organization: Interrupt Technology Corporation, Manhattan Beach, CA
Lines: 26

In article <2997.Jun2704.59.0991@kramden.acf.nyu.edu>
brnstnd@kramden.acf.nyu.edu (Dan Bernstein) writes:

> Do none of us truly understand job control? (Chris Torek
> excepted, of course. :-) )

This proves once again what a horrible design (if you can dignify it
with that word) job control is.  The BSD grad students confused the
desirable concept of being able to temporarily halt a process with the
also-desirable concept of being able to dynamically vary the
connection between the keyboard/display and various processes.  System
V's layers do a much better job of the latter for non-windowing
systems, while ignoring the former.  Windowing systems do a vastly
better of the latter, but again ignore the former.

My recommendation (which will be ignored, of course) is to trash the
horrible BSD design, keeping only the ability to stop a job, and
implement System V's "shl" for the use of those people who don't have
windows.  We should be so lucky.

P.S.  I'm directing followups to comp.unix.wizards only, since this
isn't really related to the bugs mentioned in the original posting.
Since I don't read wizards, if you *really* want to flame me you'll
have to do it by e-mail.
-- 
	Geoff Kuenning   geoff@ITcorp.com   uunet!desint!geoff