Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!decwrl!labrea!agate!ucbvax!CORY.BERKELEY.EDU!dillon
From: dillon@CORY.BERKELEY.EDU (Matt Dillon)
Newsgroups: comp.sys.amiga
Subject: Re: Processes & tasks
Message-ID: <8803182146.AA01657@cory.Berkeley.EDU>
Date: 18 Mar 88 21:46:09 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 35


>What is the difference between processes and tasks?
>
>People always seem to call a CLI a ask, when I think it is really
>a process.
>
>I presume processes are some super-structure of tasks, and that processes
>can own many tasks.
>
>Then there are interrupts ...
>

	A process is a superset of a task.  Essentially a task structure
with some additional fields that allow it to talk to DOS.  That is the
only difference.  A task can do anything a process can do with only that
one exception.

	A CLI is a process all right.

	There is also a distinction among processes.  A Processes can 
either have a CLI structure or not.  For instance, processes started from
the workbench do NOT have a CLI structure.  Processes started from a CLI
do have a CLI structure (the CLI).  In fact, if you get right down to it,
when you do something like:

	1> DIR

	The DIR command is not run as a new processes, but under the same
process running the CLI.  Only when you

	1> RUN DIR

	Does DIR get its own process (under a new CLI created by RUN).

						-Matt