From owner-freebsd-hackers  Mon Jun 17 19:39:47 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id TAA19173
          for hackers-outgoing; Mon, 17 Jun 1996 19:39:47 -0700 (PDT)
Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA19162
          for <hackers@freebsd.org>; Mon, 17 Jun 1996 19:39:43 -0700 (PDT)
Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.7.5/CET-v2.1) with SMTP id LAA07115 for <hackers@freebsd.org>; Tue, 18 Jun 1996 11:39:41 +0900 (JST)
Date: Tue, 18 Jun 1996 11:39:41 +0900 (JST)
From: Michael Hancock <michaelh@cet.co.jp>
To: hackers@freebsd.org
Subject: vfork cow?
In-Reply-To: <199606172057.NAA08544@phaeton.artisoft.com>
Message-ID: <Pine.SV4.3.93.960618105553.6804A-100000@parkplace.cet.co.jp>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

I didn't realize that vfork in 4.4bsd was implemented with copy-on-write
semantics until I read the deamon book.  Is it really going to be a
deprecated call kept around for compatibility?

-mike hancock