Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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
Date: Fri, 3 Sep 2004 12:26:24 +1000 (EST)
From: luke DOT kendall AT cisra DOT canon DOT com DOT au
Subject: Re: How to detect a broken Cygwin mirror?
To: Cygwin List <cygwin AT cygwin DOT com>
In-Reply-To: <6.1.0.6.0.20040902220900.034c27f0@pop.prospeed.net>
MIME-Version: 1.0
Content-Type: TEXT/plain; CHARSET=US-ASCII
Message-Id: <20040903022624.3BDB98454B@pessard.research.canon.com.au>

On  2 Sep, Larry Hall wrote:
>  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?

That's true, I was.  (There is no automated Uninstall method, is there?)
So it wasn't the checkdisk, it was the reboot, eh?

>  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.  

The extra security is good to have though, so we're trying to make it
all work with ntsec turned on ...

Thanks Larry,

luke


--
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/