From owner-cvs-sys  Sat Apr 12 19:44:42 1997
Return-Path: <owner-cvs-sys>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id TAA11372
          for cvs-sys-outgoing; Sat, 12 Apr 1997 19:44:42 -0700 (PDT)
Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA11355;
          Sat, 12 Apr 1997 19:44:29 -0700 (PDT)
Received: (from root@localhost) by dyson.iquest.net (8.8.4/8.6.9) id VAA03239; Sat, 12 Apr 1997 21:44:03 -0500 (EST)
From: "John S. Dyson" <toor@dyson.iquest.net>
Message-Id: <199704130244.VAA03239@dyson.iquest.net>
Subject: Re: cvs commit:  src/sys/i386/ibcs2 imgact_coff.c src/sys/i386/i386 pmap.c src/sys/i386/linux imgact_linux.c src/sys/kern imgact
In-Reply-To: <199704130231.MAA05870@freebsd1.cimlogic.com.au> from John Birrell at "Apr 13, 97 12:31:42 pm"
To: jb@cimlogic.com.au (John Birrell)
Date: Sat, 12 Apr 1997 21:44:03 -0500 (EST)
Cc: dyson@freefall.freebsd.org, CVS-committers@freefall.freebsd.org,
        cvs-all@freefall.freebsd.org, cvs-sys@freefall.freebsd.org
X-Mailer: ELM [version 2.4ME+ PL31 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-cvs-sys@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> John Dyson wrote:
> [...]
> >   Implement rfork(!RFPROC !RFMEM), which allows a thread to divorce its memory
> >   	from the other threads of a group.
> >   
> >   Implement rfork(!RFPROC RFCFDG), which closes all file descriptors, eliminating
> >   	possible existing shares with other threads/processes.
> >   
> >   Implement rfork(!RFPROC RFFDG), which divorces the file descriptors for a
> >   	thread from the rest of the group.
> >   
> >   Fix the case where a thread does an exec.  It is almost nonsense for a thread
> >   	to modify the other threads address space by an exec, so we
> >   	now automatically divorce the address space before modifying it.
> [...]
> 
> Where do these changes leave rfork(!RFPROC RFMEM !RFFDG)??? 8-)
> 
My previous response was wrong.  It won't do anything.

John