Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
From: "Chris January" <chris@atomice.net>
To: "Ralf Habacker" <Ralf.Habacker@freenet.de>
Cc: "Cygwin@Cygwin.Com" <cygwin@cygwin.com>
Subject: RE: Mozilla 1.3 built on cygwin?
Date: Sat, 5 Apr 2003 20:41:44 +0100
Message-ID: <LPEHIHGCJOAIPFLADJAHOECHDIAA.chris@atomice.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
In-Reply-To: <005101c2f7e3$915e7a00$0a1c440a@BRAMSCHE>
Importance: Normal

> > If you have such great insight into this type of thing, it won't take
> > you any time at all to duplicate.  You've been complaining about this
> > and other cygwin performance issues for months.  Why don't *you* do
> > something?  I figured fork/exec/signals out from scratch.  Certainly the
> > brighter bulbs than I who would be finding the problem would have no
> > problems generating a new and better implementation.  It's a wonder why
> > no one has done so yet.
>
> There are several people on the list with more skills as I have
> and I was hoping
> that somebody of this gurus could fix this .... I'm wondering too.
>
> It seems really it is on me to buy this Nebett book and to see,
> what I can do.
> It will need some time to get familiar with this stuff and I have
> currently two
> libtool relating outstanding tasks, which has to be finished first

You could buy the Nebett book. Or instead download the sample source code
(including the fork example) from
http://www.newriders.com/content/images/1578701996/downloads/1578701996.zip
and http://www.newriders.com/content/images/1578701996/downloads/ntdll.zip.
You can find most of the API that's documented in Nebbet's book at
http://undocumented.ntinternals.net/.

Chris


--
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/