X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Wed, 24 Sep 2008 11:29:40 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: [OT] polite response to rather rude reponse... Message-ID: <20080924152940.GG22539@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20080923143543 DOT GA6284 AT ednor DOT casa DOT cgf DOT cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.16 (2007-06-09) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Wed, Sep 24, 2008 at 03:11:28PM +0000, Robinson, Paul T (NonStop) wrote: >cgf wrote: >>We tend to react strongly to suggestions that Cygwin, which runs in user >>space, could cause something like a BSOD. Windows is far from a perfect >>OS but running a simple user program should not crash it. That doesn't >>mean that there it is impossible for a simple user program to crash it >>but if Windows crashes, it's a serious Windows bug not a program bug. > >Pedantically, it's a serious Windows bug, but does not let the program >off the hook. The program could be using Windows in some unanticipated >incorrect way. Correcting the BSOD in Windows would then change the >symptom to something less devastating, but the program would still need >to be corrected. (Speaking as someone who once took out a timesharing >system three times before the operations staff asked me nicely to stop >exercising the bug in the OS.) If you want to recite personal experiences about crashing operating systems or generically talk about programming philosophy please move to cygwin-talk. Otherwise, do some research in the Cygwin sources and you'll see just how many accommodations have been made for strange Windows behavior. No cygwin developer needs to be lectured about this. Seriously, this discussion is a rat hole. I will take drastic steps to shut it down if necessary. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/