Path: utzoo!attcan!uunet!snorkelwacker!usc!sdd.hp.com!zaphod.mps.ohio-state.edu!brutus.cs.uiuc.edu!ux1.cso.uiuc.edu!aries!mcdonald
From: mcdonald@aries.scs.uiuc.edu (Doug McDonald)
Newsgroups: comp.arch
Subject: Re: fork, spawn, vfork: an overview
Message-ID: <1990Aug8.133546.27806@ux1.cso.uiuc.edu>
Date: 8 Aug 90 13:35:46 GMT
References: <25904@mimsy.umd.edu> <12382@encore.Encore.COM> <1940@charon.cwi.nl>
Sender: usenet@ux1.cso.uiuc.edu (News)
Reply-To: mcdonald@aries.scs.uiuc.edu (Doug McDonald)
Organization: School of Chemical Sciences, Univ. of Illinois at Urbana-Champaign
Lines: 9

In article <1940@charon.cwi.nl> jack@cwi.nl (Jack Jansen) writes:
>A reasonably clean solution to the vfork() 

PLEASE folks, this is not a computer architecture issue. It is a
question that has to do with the software of one very particular
operating system. Let's move it appropriate os-specific group? OK.
Most OS's don;t seem to have any such weird difficulties.

Doug MCDonald