Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
From:	"Ralf Habacker" <Ralf DOT Habacker AT freenet DOT de>
To:	<cygwin AT cygwin DOT com>
Subject:	RE: Mozilla 1.3 built on cygwin?
Date:	Tue, 1 Apr 2003 02:13:48 +0200
Message-ID:	<005101c2f7e3$915e7a00$0a1c440a@BRAMSCHE>
MIME-Version:	1.0
X-Priority:	3 (Normal)
X-MSMail-Priority:	Normal
Importance:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4133.2400
In-Reply-To:	<20030329222031.GA23834@redhat.com>

> 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

Ralf








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

- Raw text -