X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_HELO_PASS X-Spam-Check-By: sourceware.org Message-ID: <20100913180927.38461qa6l2tbt1og@webmail.df.eu> Date: Mon, 13 Sep 2010 18:09:27 +0200 From: Markus Hoenicka To: cygwin AT cygwin DOT com Subject: Re: Cygwin instabilities References: <4C8E3A4B DOT 8030909 AT cygwin DOT com> <20100913173648 DOT 15137e2d0sfh16o0 AT webmail DOT df DOT eu> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: domainFACTORY X-Df-Sender: 472582 X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Al was heard to say: > No that is not the way to go. I think there are people which run > Cygwin on more than 1 machine, so they have a personal estimation and > experience. > Yes, and this is where the Cygwin archives come in handy. If there are users running Cygwin on lots of machines, they are likely to run into problems once in a while, and they're likely to use the list for reporting these problems. If Cygwin was as instable as you apparently suspect, you'd find plenty of reports in the archives. I haven't noticed any such large-scale reports about instabilities in several years of lurking on this list, but your thorough perusal of the archives may well prove me wrong. regards, Markus -- Markus Hoenicka http://www.mhoenicka.de AQ score 38 -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple