Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!ucsd!ucsdhub!hp-sdd!ncr-sd!ncrlnk!ncrcce!pasek
From: pasek@ncrcce.StPaul.NCR.COM (Michael A. Pasek)
Newsgroups: comp.arch
Subject: Re: fork()
Summary: Wrong newsgroup !
Keywords: fork() unix
Message-ID: <1942@ncrcce.StPaul.NCR.COM>
Date: 2 Mar 90 16:16:23 GMT
Expires: 9 Mar 90 05:00:00 GMT
References: <37873@cornell.UUCP>
Reply-To: pasek@c10sd3.StPaul.NCR.COM (M. A. Pasek)
Followup-To: comp.sys.unix
Distribution: comp
Organization: NCR Comten, Inc.
Lines: 10

In article <37873@cornell.UUCP> huff@cs.cornell.edu (Richard Huff) writes:
>I guess that most people are used to using fork() [remainder of a very
> long article regarding a Unix system call, its faults, and a proposed
> solution have been deleted]

What does this have to do with comp.arch ?  PLEASE keep OS-specific or
language-specific stuff in its appropriate (its own) newgroup.  If there
isn't one, use comp.misc.....

M. A. P.