From owner-freebsd-current  Thu Apr 18 09:27:22 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id JAA15808
          for current-outgoing; Thu, 18 Apr 1996 09:27:22 -0700 (PDT)
Received: from xi.dorm.umd.edu (root@xi.dorm.umd.edu [129.2.152.45])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id JAA15800
          for <current@freebsd.org>; Thu, 18 Apr 1996 09:27:20 -0700 (PDT)
Received: from localhost (smpatel@localhost [127.0.0.1]) by xi.dorm.umd.edu (8.7.5/8.6.12) with SMTP id MAA16398; Thu, 18 Apr 1996 12:27:10 -0400 (EDT)
Date: Thu, 18 Apr 1996 12:27:08 -0400 (EDT)
From: Sujal Patel <smpatel@umiacs.umd.edu>
X-Sender: smpatel@xi.dorm.umd.edu
To: Garrett Wollman <wollman@lcs.mit.edu>
cc: current@freebsd.org
Subject: Re: Changes for vfork()
In-Reply-To: <9604181607.AA06704@halloran-eldar.lcs.mit.edu>
Message-ID: <Pine.NEB.3.92.960418122537.5890j-100000@xi.dorm.umd.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Thu, 18 Apr 1996, Garrett Wollman wrote:

> and everything should Just Work.  (Make sure to do all of these steps
> before recompiling the world, though.)

We should briefly look over the source tree too.  Some brain-dead programs
may rely on vfork() behavior (such as sleeping on the child, or altering
the parent's address space)...

Other then that, What you posted is exactly what I was thinking--  Unless
there are any objections, I'll take care of it in the next few days.


Sujal