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, 27 May 2001 01:49:13 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin-xfree AT cygwin DOT com, cygwin AT cygwin DOT com
Subject: Re: bluescreen during XF86/cygwin build
Message-ID: <20010527014913.A13495@redhat.com>
Reply-To: cygwin-xfree AT cygwin DOT com
Mail-Followup-To: cygwin-xfree AT cygwin DOT com, cygwin AT cygwin DOT com
References: <002501c0e662$0ed24a60$6800a8c0 AT dbca950> <016b01c0e662$415f9320$0200a8c0 AT lifelesswks> <003d01c0e665$9e71aff0$6800a8c0 AT dbca950> <20010527003757 DOT A12171 AT redhat DOT com> <004d01c0e669$152d0380$6800a8c0 AT dbca950>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.11i
In-Reply-To: <004d01c0e669$152d0380$6800a8c0@dbca950>; from dcook@caveduck.com on Sat, May 26, 2001 at 09:54:16PM -0700

On Sat, May 26, 2001 at 09:54:16PM -0700, Dave Cook wrote:
>Chris Faylor wrote:
>>>I realize that cygwin doesn't install any actual drivers, but it pushes
>>>the filesystem in ways that W2K may not expect :)
>>
>>No, it doesn't actually.  It just uses standard Win32 API calls.
>>
>>With an OS like W2K there is really no way that Cygwin should be able
>>to cause a blue screen.  If it does, it's an OS bug, not a Cygwin bug.
>
>You can't necessarily just tell the customer "it's Microsoft's
>problem".

1) You are not "the customer".

2) I *can* tell you that it is Microsoft's problem if I can write an
   unprivileged program that crashes their OS.  There is no way that I
   am going to accomodate a Microsoft blue screen problem on Windows NT
   in Cygwin.  I might consider it on an "OS" like Windows 9x but NT/2K
   is an OS without the quotes.

>From a customer centric view, if I can run command X on a normally
>configured Linux box and it works, but the same supposedly supported
>command fails in Cygwin, then it's a Cygwin problem (though perhaps
>technically not a Cygwin bug).

You really are out to lunch on this one.  You downloaded some free
software from a web site.  That gives you *zero* rights.

If you think that this is in some way related to Red Hat Linux or that
this is a commercial product in any way, you are sadly mistaken.

So, my official answer *is* that this is either Microsoft's problem or
your problem.  It looks like Robert Collins is graciously offering to
help you.  He is a volunteer, like me.  You are lucky that he is
interested and I'm glad that he is helping you but it is unlikely that
if you find that it is, say, the MoveFileEx call that is causing
problems that I will do anything to fix it in Cygwin.

Of course, I do trust Robert's opinion so if he thinks that we need
to fix something in Cygwin, I'll listen.  I just won't put in 200 lines
of code to work around a bug in 2K.

cgf

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple