Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Date:	Sun, 9 Sep 2001 19:59:19 -0400
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: vfork problems on Win98 -- is there a fix?
Message-ID:	<20010909195919.E11565@redhat.com>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<F1749GuV2C6rhMnPLg80000a8fd AT hotmail DOT com>
Mime-Version:	1.0
In-Reply-To:	<F1749GuV2C6rhMnPLg80000a8fd@hotmail.com>
User-Agent:	Mutt/1.3.21i

On Sun, Sep 09, 2001 at 04:50:08PM -0700, Andrew Kalman wrote:
>>The bottom line, cruel as it sounds is "I don't feel like it." This is
>>not an issue for the way that Red Hat uses cygwin so it is not part of
>>my official job.
>etc.
>
>Fair enough -- there's nothing wrong with prioritizing one's work.
>
>Also, the same fault occurs in Win2000 -- it's not just a Win98 issue.

I have never seen anything remotely like this on Windows 2000.  I use
it extensively.

This is YA reason for someone who is having to problem to debug it.

But, I understand that there is not a single solitary person in the entire
cygwin mailing list community who is capable of doing that.

Too bad...

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/

- Raw text -