From owner-freebsd-current  Tue Apr 22 19:09:46 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id TAA25625
          for current-outgoing; Tue, 22 Apr 1997 19:09:46 -0700 (PDT)
Received: from root.com (implode.root.com [198.145.90.17])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA25617
          for <current@freebsd.org>; Tue, 22 Apr 1997 19:09:37 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by root.com (8.8.5/8.6.5) with SMTP id TAA00458; Tue, 22 Apr 1997 19:11:14 -0700 (PDT)
Message-Id: <199704230211.TAA00458@root.com>
X-Authentication-Warning: implode.root.com: localhost [127.0.0.1] didn't use HELO protocol
To: "John S. Dyson" <toor@dyson.iquest.net>
cc: sef@Kithrup.COM (Sean Eric Fagan), current@freebsd.org
Subject: Re: Recent vfork kernel changes broke csh & tcsh! 
In-reply-to: Your message of "Tue, 22 Apr 1997 19:24:54 CDT."
             <199704230024.TAA02998@dyson.iquest.net> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Tue, 22 Apr 1997 19:11:14 -0700
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>>
>> Am I the only one who thinks that restoring behaviour known to be a defect
>> in the original implementation is a BAD idea?
>> 
>I don't think that you are the only one.  However, it makes a difference
>of about 3mins out of 1:51 for make world.
>
>I am backing it out anyway.

   Perhaps rfork() should be called directly instead in areas where it is
known to be safe (certain shells, etc).

-DG

David Greenman
Core-team/Principal Architect, The FreeBSD Project