Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!ucsd!sdcsvax!net1!hutch
From: hutch@net1.ucsd.edu (Jim Hutchison)
Newsgroups: comp.sys.amiga
Subject: Fork -- semi-possible
Keywords: semi-pro banana eating simian
Message-ID: <4982@sdcsvax.UCSD.EDU>
Date: 27 May 88 09:34:47 GMT
References: <10289@stb.UUCP>
Sender: nobody@sdcsvax.UCSD.EDU
Reply-To: hutch@net1.UUCP (Jim Hutchison)
Lines: 17

Ports?  Oh my!  Yes, in the heavy duty sense you have to dup all of the
parents resources (including program data space).  For the average use,
things can be much simpler.

I'm porting things (junk, stuff, tidbits).  I only need to have wait() wait,
and fork() start up a second task.  This will get me going for the
fork()/exec() crew.  I would rather munge as little code as possible.

Admittedly I may be misunderstanding again (like when I didn't know about
scatter loading :-( for program loading), but shouldn't this work o.k.?
All I want is a new *seperate* process which I can examine for signs of life.

Comments?
--
    Jim Hutchison   		UUCP:	{dcdwest,ucbvax}!cs!net1!hutch
		    		ARPA:	Hutch@net1.ucsd.edu
Disclaimer:  The cat agreed that it would be o.k. to say these things.