Messages in this thread | | | From | "Anthony Barbachan" <> | Subject | Re: Porting vfork() | Date | Fri, 8 Jan 1999 00:59:26 -0500 |
| |
-----Original Message----- From: Chris Wedgwood <cw@ix.net.nz> To: kernel@draper.net <kernel@draper.net> Cc: linux-kernel@vger.rutgers.edu <linux-kernel@vger.rutgers.edu> Date: Thursday, January 07, 1999 3:27 PM Subject: Re: Porting vfork()
>On Tue, Jan 05, 1999 at 03:46:11PM -0600, kernel@draper.net wrote: > >> As of late the "different" vfork() behavior in Linux is appearing >> as a porting problem more often than expected (by me). > >Specifically, what is breaking? >
I'm not sure either, but perl seams to think so. Its configure script defaults to a broken vfork() on Linux.
>Most applications I've seen that use vfork seem to work without any >changes here.... > > > >-cw > >- >To unsubscribe from this list: send the line "unsubscribe linux-kernel" in >the body of a message to majordomo@vger.rutgers.edu >Please read the FAQ at http://www.tux.org/lkml/ >
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |