From owner-freebsd-current Sat Apr 20 18:55:06 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA15071 for current-outgoing; Sat, 20 Apr 1996 18:55:06 -0700 (PDT) Received: from haywire.DIALix.COM (root@haywire.DIALix.COM [192.203.228.65]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id SAA15057 for ; Sat, 20 Apr 1996 18:54:57 -0700 (PDT) Received: (from news@localhost) by haywire.DIALix.COM (8.7.5/8.7.3) id JAA26235 for freebsd-current@freebsd.org; Sun, 21 Apr 1996 09:55:01 +0800 (WST) X-Authentication-Warning: haywire.DIALix.COM: news set sender to usenet-request@haywire.dialix.com using -f Received: from GATEWAY by haywire.DIALix.COM with netnews for freebsd-current@freebsd.org (problems to: usenet@haywire.dialix.com) To: freebsd-current@freebsd.org Date: 21 Apr 96 01:50:45 GMT From: peter@jhome.DIALix.COM (Peter Wemm) Message-ID: Organization: DIALix Services, Perth, Australia. References: <9604181607.AA06704@halloran-eldar.lcs.mit.edu>, Subject: Re: Changes for vfork() Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk smpatel@umiacs.umd.edu (Sujal Patel) writes: >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)... Note that there are some programs still using these features.. tcsh, for one, uses the shared address space semantics to update some statistics in the parent. Naturally, this does not work on FreeBSD, because of the incomplete vfork() emulation. It's ironic.. vfork() was a traditional BSD thing, and now System V machines implement it better than the current BSD's do. >Sujal -Peter