X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org From: "Robinson, Paul T (NonStop)" To: "cygwin@cygwin.com" Date: Wed, 24 Sep 2008 15:11:28 +0000 Subject: RE: [OT] polite response to rather rude reponse... Message-ID: References: <20080923143543.GA6284@ednor.casa.cgf.cx> In-Reply-To: <20080923143543.GA6284@ednor.casa.cgf.cx> Accept-Language: en-US Content-Language: en-US acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id m8OFDLl4006297 >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.) --paulr -- 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/