Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Reply-To: Cygwin List Message-Id: <6.1.0.6.0.20040902220900.034c27f0@pop.prospeed.net> X-Sender: Date: Thu, 02 Sep 2004 22:14:08 -0400 To: luke DOT kendall AT cisra DOT canon DOT com DOT au, cygwin AT cygwin DOT com From: Larry Hall Subject: Re: How to detect a broken Cygwin mirror? In-Reply-To: <20040903014127.6FBDC8454B@pessard.research.canon.com.au> References: <20040903014127 DOT 6FBDC8454B AT pessard DOT research DOT canon DOT com DOT au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" At 09:41 PM 9/2/2004, you wrote: >They also say it's common for it to be very, very hard to remove >C:\cygwin - unable to remove it, unable to take ownership, on occasion >having to boot into safe mode to get rid of it (on the way to trying a >fresh Cygwin install, you see). Perhaps you're running one of Cygwin's service apps (sshd, crond, etc?) and you didn't stop it before doing the remove? Otherwise, this sounds like a simple permissions issue. If you're getting files installed that indicate no permissions, you might want to try setting 'nontsec' in your CYGWIN environment variable prior to the install. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- 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/