X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org From: "Wes S" To: cygwin AT cygwin DOT com Date: Mon, 26 May 2008 20:06:31 -0400 MIME-Version: 1.0 Subject: Re: Why I hate updates Message-ID: <483B1847.27258.12E3D6E1@wess.acegroup.cc> In-reply-to: <1211846188.16349.107.camel@sd> References: <1211808501 DOT 4769 DOT ezmlm AT cygwin DOT com>, <1211846188 DOT 16349 DOT 107 DOT camel AT sd> X-mailer: Pegasus Mail for Windows (4.41) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-IsSubscribed: yes 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 26 May 2008 at 13:56, Richard Foulk wrote: > I've asked a few update related questions over the years and mostly > gotten > no answers. I now update only occasionally and expect to have to reload > and reconfigure from time to time. > > That's just the way it goes. Setup doesn't even recover from failed > file transfers very well. Often blows the whole system or causes > setup to be unable to run again, requiring a fresh install. A setup > error *usually* means starting over from scratch. > > Not a very production-friendly system. > Well if it is important to you, you test an update on a parrellel system. I do that at home as I once did at work. Remember you are part of the effort and a beta tester. No pain, no gain. Wes -- 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/