Date: Wed, 16 Apr 1997 09:41:07 -0500 (EST) From: "John S. Dyson" <toor@dyson.iquest.net> To: bsdcur@shadows.aeon.net (mika ruohotie) Cc: toor@dyson.iquest.net, current@freebsd.org Subject: Re: You will need to recompile your libc and apps!!! Message-ID: <199704161441.JAA04688@dyson.iquest.net> In-Reply-To: <199704161428.RAA15306@shadows.aeon.net> from mika ruohotie at "Apr 16, 97 05:28:12 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
> > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199704161441.JAA04688>