From owner-freebsd-current  Fri Apr 19 07:18:05 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id HAA07683
          for current-outgoing; Fri, 19 Apr 1996 07:18:05 -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 HAA07674
          for <current@FreeBSD.ORG>; Fri, 19 Apr 1996 07:18:02 -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 KAA02838; Fri, 19 Apr 1996 10:17:24 -0400 (EDT)
Date: Fri, 19 Apr 1996 10:17:24 -0400 (EDT)
From: Sujal Patel <smpatel@umiacs.umd.edu>
X-Sender: smpatel@xi.dorm.umd.edu
To: Lars Gerhard Kuehl <lars@elbe.desy.de>
cc: current@FreeBSD.ORG
Subject: Re: Changes for vfork()
In-Reply-To: <9604191322.AA07511@elbe.desy.de>
Message-ID: <Pine.NEB.3.92.960419101637.1260D-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 Fri, 19 Apr 1996, Lars Gerhard Kuehl wrote:

> The current vfork() already doesn't allow the child to alter the parent's
> address space and sometimes it's very desirable (or at least convenient)
> if one can rely on the parent being suspended until the child calls
> execve() or _exit().

Convenient perhaps, but this is by no means correct (or desirable).  If
you really want to alter the parent's address space, you should fork with
rfork (RFPROC|RFMEM)


Sujal