From owner-freebsd-current Wed Apr 16 07:41:45 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id HAA00568 for current-outgoing; Wed, 16 Apr 1997 07:41:45 -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 HAA00559 for ; Wed, 16 Apr 1997 07:41:40 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.8.4/8.6.9) id JAA04688; Wed, 16 Apr 1997 09:41:07 -0500 (EST) From: "John S. Dyson" Message-Id: <199704161441.JAA04688@dyson.iquest.net> Subject: Re: You will need to recompile your libc and apps!!! In-Reply-To: <199704161428.RAA15306@shadows.aeon.net> from mika ruohotie at "Apr 16, 97 05:28:12 pm" To: bsdcur@shadows.aeon.net (mika ruohotie) Date: Wed, 16 Apr 1997 09:41:07 -0500 (EST) Cc: toor@dyson.iquest.net, current@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-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > be committing the fix to vfork until people have a chance to recompile > > their libc and re-link their apps with the corrected library. > > > > If you try to use the new (semantically correct) vfork with the broken library, > > you will experience some unexpected hangs in apps that use popen once in a > > is this something that gets fixed with a make world? or do i need to twiddle > something before that? or after? or during? =) > It will get fixed during a make world, but the reason for the warning is for those that don't normally think of serious dependencies between the kernel and libc. Usually, it is safe, but the popen broke something in a true vfork. Vfork is still problematical in the general case, but does work now in it's normally intended uses, with the compile environment that we use. John