Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!uwvax!uwmacc!hobbes!root
From: root@hobbes.UUCP
Newsgroups: comp.arch,comp.unix.wizards,comp.os.minix
Subject: Re: Free Software Foundation (was: Re: Mach, the new standard?)
Message-ID: <233@hobbes.UUCP>
Date: Thu, 24-Sep-87 23:40:33 EDT
Article-I.D.: hobbes.233
Posted: Thu Sep 24 23:40:33 1987
Date-Received: Sat, 26-Sep-87 15:09:09 EDT
References: <1665@ncr-sd.SanDiego.NCR.COM> <8381@utzoo.UUCP>
Reply-To: root@hobbes.UUCP (John Plocher)
Followup-To: comp.arch
Organization: U of Wisconsin - Madison  Spanish Department
Lines: 12
Xref: utgpu comp.arch:2203 comp.unix.wizards:4153 comp.os.minix:1639

> Most uses of fork() are immediately followed by an exec() call.

When this came up last spring, someone (gwyn?) grep'd thru all the Unix
source and found a grand total of TWO places where fork() was immediately
followed by exec()!  All the others had dup()s, close()s, and setuid()s, etc
stuck in between.  In the future, please try to ground your "facts" in
something solid before making sweeping statements like that...

   John

-- 
John Plocher uwvax!geowhiz!uwspan!plocher  plocher%uwspan.UUCP@uwvax.CS.WISC.EDU