Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/5/84; site SCIRTP.UUCP
Path: utzoo!linus!philabs!cmcl2!seismo!harvard!talcott!panda!genrad!decvax!mcnc!rti-sel!SCIRTP!dfh
From: dfh@SCIRTP.UUCP (David F. Hinnant)
Newsgroups: net.unix-wizards
Subject: Putting Job Control in System V?
Message-ID: <267@SCIRTP.UUCP>
Date: Thu, 1-Aug-85 14:04:16 EDT
Article-I.D.: SCIRTP.267
Posted: Thu Aug  1 14:04:16 1985
Date-Received: Sun, 4-Aug-85 04:44:42 EDT
Distribution: net
Organization: SCI Systems, Research Triangle Park, NC
Lines: 40


  We're contemplating putting job control into our generic System V kernel.
We would like opinions on what changes we would have to make to add:

  1)  System V.2 style job control with shell layers (shl) using
      pseudo-ttys.

  2)  BSD style job control with the C shell.

  Specificly:

  Our initial impression is that it would be easier to put System V.2
style job control in.  Is this a valid assumption?

  In comparing the two styles, what are the design tradeoffs?
implementation differences?  Would you do one or the other or both if
given the choice?

  How difficult would it be to add the additional signals needed by BSD
style job control and other changes to a System V kernel?  What exactly
are the changes other than additional signals and a new line discipline?

  I've heard rumors of V.2 job control bugs when it first came out. 
Something to do with the sticky bit?  Could someone explain exactly what
went on?  Do the problems still exist?

  Will System V.3 have the V.2 style job control, or will it be different?
Does anyone know?  Will System V.3 have sockets?

  Which style job control does the Korn shell use?

  As always, I'll summarize and post any mailed response I receive.


				Thanks in advance

-- 
				David Hinnant
				SCI Systems, Inc.
				{decvax, akgua}!mcnc!rti-sel!scirtp!dfh