home *** CD-ROM | disk | FTP | other *** search
- From: seismo!hadron!jsdy@sally.utexas.edu (Joseph S. D. Yao)
- Date: Tue, 4 Nov 86 22:47:30 est
- Organization: Hadron, Inc., Fairfax, VA
-
- In article <6176@ut-sally.UUCP> you write:
- >From: seismo!mcvax!jack
- >Organization: AMOEBA project, CWI, Amsterdam
- >Date: Tue, 28 Oct 86 23:39:03 +0100
- >
- >*CURRENT JOB CONTROL IMPLEMENTATIONS ARE HORRIBLE. HORRIBLE!
- >HORRIBLE!!!!!!!!*
- >Both solutions are filled with horrible tricks like closing
- >tty's and re-opening them and then doing funny ioctl()s and the closing
- >them again and then reopening then and then...
- >It is of course a praiseworthy feat that the folks at HP managed to
- >sqeeze those two horrible, inconsistent, unintellegible mechanisms
- >into one poor kernel, but I'm afraid the result is horrible**2.
- >>From now on, you can find me in the "job control is horrible" camp.
-
- Jack, one gets the vague feeling you dislike these implementations,
- without the least notion why. Could you please meditate, or take a
- pill, or whatever soothes you, and then tell us exactly why you feel
- this way? (You may wish to take frequent mellow breaks.) Perhaps
- you could also tell us what you feel defines a non-horrible job
- control implementation. Thank you!
- --
-
- Joe Yao hadron!jsdy@seismo.{CSS.GOV,ARPA,UUCP}
- jsdy@hadron.COM (not yet domainised)
-
- Volume-Number: Volume 8, Number 41
-
-