Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Thu, 31 Jan 2002 14:58:23 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: A real fork() on NT Message-ID: <20020131195823.GM7966@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20020131042428 DOT GB5472 AT redhat DOT com> <006801c1aa8d$16104440$01000001 AT BRAMSCHE> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <006801c1aa8d$16104440$01000001@BRAMSCHE> User-Agent: Mutt/1.3.23.1i On Thu, Jan 31, 2002 at 08:25:47PM +0100, Ralf Habacker wrote: >>On Wed, Jan 30, 2002 at 07:50:45PM -0800, Barubary wrote: >>>Do you have any idea how to compile a program for the win32 POSIX >>>system? If we could reverse engineer a win32 POSIX program that uses >>>fork(), we could see the raw NT commands to do it. >> >>Corinna already provided a reference which provided you with a sample >>of a Windows NT version of fork. >> >>Just buy the book and you're all set. >> >What about this approach using threads >http://www.xav.com/perl/lib/Pod/perlfork.html Given all of the caveats at that page, it's hard to understand how it could be a general solution. What about someone actually familiarizing themselves with how Cygwin does things currently? Then they can make some informed suggestions. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/