delorie.com/archives/browse.cgi | search |
X-Recipient: | archive-cygwin AT delorie DOT com |
X-SWARE-Spam-Status: | No, hits=-1.4 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,T_TO_NO_BRKTS_FREEMAIL |
X-Spam-Check-By: | sourceware.org |
MIME-Version: | 1.0 |
In-Reply-To: | <20100913173648.15137e2d0sfh16o0@webmail.df.eu> |
References: | <AANLkTim+hU+Cg6_J83B_h9VHsL8wiC4Xh7TbcwzjSjkW AT mail DOT gmail DOT com> <4C8E3A4B DOT 8030909 AT cygwin DOT com> <AANLkTimX-AztuJvS-RG+bZqWCVN7tEdQXs6Ogw_fCZC5 AT mail DOT gmail DOT com> <20100913173648 DOT 15137e2d0sfh16o0 AT webmail DOT df DOT eu> |
Date: | Mon, 13 Sep 2010 10:48:03 -0500 |
Message-ID: | <AANLkTinaBT8HDbjQeAuwcV_4=6NYMWAxi5QHw4hzZ4Ti@mail.gmail.com> |
Subject: | Re: Cygwin instabilities |
From: | mike marchywka <marchywka AT gmail DOT com> |
To: | cygwin AT cygwin DOT com |
X-IsSubscribed: | yes |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Id: | <cygwin.cygwin.com> |
List-Unsubscribe: | <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com> |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sourceware.org/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs> |
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 9/13/10, Markus Hoenicka <markus.hoenicka xxx.duh> wrote: > Al <oss DOT elmar AT xxx DOT xxx> was heard to say: > >> I am not asking this to debug my own setup. I am rather ask for an >> overall estimation of Cygwins current and future usability and >> stability. >> > > These two things are related. Remember that Cygwin is an open source > project, and that it does not employ dozens of developers with the > abstract task of increasing usability or stability. Both are increased > by either debugging or at least properly reporting bugs. If you > experience stability problems on your setup, then reporting this in > all necessary detail is a sure step to increase future usability and > stability. > >> It not, how to tweak Cygwin to run on some machines. It's, how big is >> the percentage of windows machines, that will run a stable Cygwin with >> the standard setup.exe setup. > > Who would keep counters of stable or instable setups? These number are > exceptionally hard to come by. Even if this list is now flooded with > "my setup works" and "mine too" posts, these numbers would not be > representative. Users may have given up on Cygwin due to instabilities > without notifying the list. Others may run Cygwin so happily they > never think about joining the list. All you could do is to scan the > Cygwin archives for "instabilities" (this is your term and arguably > far too unspecific) and compare it to the number of instabilities > reported for any run-of-the mill Linux in the same timeframe. I would mention in response to earlier question that I'm quite happy with cygwin on 'doze 7. I routinely build and test mobile phone apps here as well as miscellaneous script based downloads and everything seems fine. The performance issues I reported are fine compared to any 'doze alternatives and so far most of what I have developed under cygwin runs under real linux. And it is a good way to learn linux too LOL. btw, is is possible to do something like the new iproute2 stuff in dohs? > > Just my 2cc > > Markus > > P.S. mine works > -- 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
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |