Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Date: Thu, 21 Nov 2002 18:34:32 -0500
From: Christopher Faylor <cgf@redhat.com>
To: cygwin@cygwin.com
Subject: Re: old cygwin distributions
Message-ID: <20021121233432.GF26759@redhat.com>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <022101c291aa$97665890$78d96f83@pomello> <7916445640.20021121213235@huno.net> <01c901c291a1$476f16a0$78d96f83@pomello> <1119233000.20021121221902@huno.net> <022101c291aa$97665890$78d96f83@pomello> <5.1.0.14.2.20021121143225.02ac95f0@pop3.cris.com> <7825298296.20021122000007@huno.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <7825298296.20021122000007@huno.net>
User-Agent: Mutt/1.5.1i

On Fri, Nov 22, 2002 at 12:00:07AM +0100, thomas wrote:
>Randall R Schulz <rrschulz@cris.com> wrote:
>>This is especially true since you're using software that has no Cygwin
>>maintainer.  Have you consulted with the development team for
>>"cdrecord?"
>
>cdrecord is contributed, so i guess that counts as 1/4 officialy
>supported :) i did contact the developer of cdrecord, j?rg schilling,
>and as mentioned in my first post he thinks this is a cygwin scheduling
>bug.  in fact he asked me to make a bug report to the mailing list.

And, that's part of the problem.  The words "cygwin scheduling bug" make
very little sense.  Cygwin is not an OS which schedules things.  There
was also a mention of fifos, which doesn't make sense in a cygwin
context.

The bottom line is that I tend to ignore problems where the description
makes no sense.  It's a simple fact of life that we have to pick and
choose what we do if we want to sleep 7 hours a night.

Out of curiousity, have you tried the most recent cygwin snapshot?  I'm
wondering if "scheduling bug" translates into "emacs cygwin is using
100% of my CPU".  That bug is supposed to be fixed in cygwin snapshots.

cgf
--
Please do not send me personal email with cygwin questions or observations.
Use the resources at http://cygwin.com/ .

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

