Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!mit-eddie!bu-cs!halleys!ulowell!page
From: page@ulowell.cs.ulowell.edu (Bob Page)
Newsgroups: comp.sys.amiga
Subject: Re: Making a Task a Process (was: Message ports in 68000)
Message-ID: <1251@ulowell.cs.ulowell.edu>
Date: Mon, 4-May-87 11:34:26 EDT
Article-I.D.: ulowell.1251
Posted: Mon May  4 11:34:26 1987
Date-Received: Tue, 5-May-87 01:55:38 EDT
References: <9663@decwrl.DEC.COM>
Reply-To: page@ulowell.cs.ulowell.edu (Bob Page)
Organization: University of Lowell
Lines: 15

jmsynge@sqm.dec.com (James M Synge) wrote in article <9663@decwrl.DEC.COM>:
>What I want (and am slowly working on) is a library of routines which a TASK
>can call which enable it to do all disk related activity just like a PROCESS.

Way back in memory (out of my cache, sorry) I seem to remember a routine
that either Flip or AndyF posted to allow a TASK to become a PROCESS,
presumably by just setting up a Process structure and gluing the TASK
structure onto it.

I (quickly) searched through my files but came up empty-handed.
Was I just dreaming this?

..Bob
-- 
Bob Page, U of Lowell CS Dept.   page@ulowell.{uucp,edu,csnet}