Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!husc6!think!ames!ucbcad!ucbvax!cbosgd!cblpf!cbstr1!Karl.Kleinpaste
From: Karl.Kleinpaste@cbstr1.att.com
Newsgroups: comp.sources.wanted
Subject: Re: C shell for System V
Message-ID: <300@cbstr1.att.com>
Date: Wed, 15-Jul-87 21:52:15 EDT
Article-I.D.: cbstr1.300
Posted: Wed Jul 15 21:52:15 1987
Date-Received: Sat, 18-Jul-87 04:37:54 EDT
References: <9904@duke.cs.duke.edu> <242@wrs.UUCP>
Sender: karl@cbstr1.att.com
Lines: 26
In-reply-to: dg@wrs.UUCP's message of 14 Jul 87 18:32:09 GMT


dg@wrs.UUCP writes:
   >[SysV csh wanted.]

   Could be a problem - as far as I know only BSD UNIX supports job control
   which was one of the main reasons for the C shell.

No, the csh was written before BSD had job control.  Pieces of it
predate the existence of anything identifiable as "BSD."  Job control
was hacked in (somewhat crudely, in my opinion; little bits and pieces
of it seem to be all over the place) when 4BSD came along.

   AT&T Unix variations
   simply don't have it.

Yes and no.  SysV doesn't support SIGTSTP and friends, of course.  But
I've mentioned from time to time (as have others) that you can go a
long way toward simulating job control using ptrace(2).  My port of
csh (landlocked inside AT&T, sigh) does this.  From the user's point
of view, it is very nearly indistinguishable from 4BSD.

   P.S. I may be wrong about BSD being the only UNIX with job control
   in which case I've got my asbestos suit ready :-)

No asbestos needed, just a little erroneous history...

Karl