Path: utzoo!utgpu!attcan!uunet!lll-winken!lll-lcc!ames!ncar!unmvax!tut.cis.ohio-state.edu!ukma!david
From: david@ms.uky.edu (David Herron -- One of the vertebrae)
Newsgroups: comp.sys.amiga
Subject: Re: Job Control not needed(indeed?)
Message-ID: <10767@s.ms.uky.edu>
Date: 30 Dec 88 04:25:40 GMT
References: <3881@pt.cs.cmu.edu> <2408@kalliope.rice.edu>
Reply-To: david@ms.uky.edu (David Herron -- One of the vertebrae)
Organization: U of Kentucky, Mathematical Sciences
Lines: 28

In article <2408@kalliope.rice.edu> phil@Rice.edu (William LeFebvre) writes:
>In article <3881@pt.cs.cmu.edu> mjw@f.gp.cs.cmu.edu (Michael Witbrock) writes:
>>ditto@cbmvax
>>>Of course, AmigaDos doesn't have job control, either, and people
>>>get along fine without it there....
>>
>>...It'd also be nice to be able to put things into the 
>>background after you start them.
>
>So start up another shell-in-a-window.


Job control is oh so much more than just being able to use ^Z and fg
and bg to "control jobs".  It's being able to make a process stop
deat in it's tracks and being able to start it back up later.

Now maybe it'd be better to do this a la the /proc type stuff of
the later versions of research Unix.  (That is, open /proc/<proc-id>
and do an ioctl(fd,..STOP..,..) rather than signal(proc-id,SIGSTOP))

Yeh I prefer having multiple "jobs" by way of windows and mice and
that kind of thing.  I *ALSO* like to be able to stop and start processes
at will and sometimes use that capability by itself from time to time.
-- 
<-- David Herron; an MMDF guy                              <david@ms.uky.edu>
<-- ska: David le casse\*'      {rutgers,uunet}!ukma!david, david@UKMA.BITNET
<-- Now I know how Zonker felt when he graduated ...
<--          Stop!  Wait!  I didn't mean to!