Path: utzoo!attcan!uunet!ncrlnk!ncr-sd!hp-sdd!ucsdhub!ucsd!nosc!helios.ee.lbl.gov!lll-tis!ames!mailrus!ncar!gatech!ulysses!hector!ekrell
From: ekrell@hector.UUCP (Eduardo Krell)
Newsgroups: comp.unix.wizards
Subject: Re: System V Release 4.0 Developers
Message-ID: <10713@ulysses.homer.nj.att.com>
Date: 11 Oct 88 12:48:30 GMT
References: <8658@smoke.ARPA> <216100004@s.cs.uiuc.edu>
Sender: netnews@ulysses.homer.nj.att.com
Reply-To: ekrell@hector.UUCP (Eduardo Krell)
Organization: AT&T Bell Laboratories
Lines: 14

In article <216100004@s.cs.uiuc.edu> carroll@s.cs.uiuc.edu writes:

>I'm sorry, I missed something here. My understanding is that it is the OS
>that supports job control (or not), not the shell.

it's both. That is, job control is needed in the kernel and the shell
has to know what to do when you type ^Z or fg or bg, etc. ksh supports
job control ONLY WHEN the underlying operating system does. If you take
a vanilla bourne shell and compile it on a system with job control,
you won't get a shell with job control support.
    
Eduardo Krell                   AT&T Bell Laboratories, Murray Hill, NJ

UUCP: {att,decvax,ucbvax}!ulysses!ekrell  Internet: ekrell@ulysses.att.com