Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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 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: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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/