This is the mail archive of the
mailing list for the Cygwin project.
Re: How to detect a broken Cygwin mirror?
- From: Larry Hall <lh-no-personal-replies-please at cygwin dot com>
- To: luke dot kendall at cisra dot canon dot com dot au, cygwin at cygwin dot com
- Date: Thu, 02 Sep 2004 22:14:08 -0400
- Subject: Re: How to detect a broken Cygwin mirror?
- References: <20040903014127.6FBDC8454B@pessard.research.canon.com.au>
- Reply-to: Cygwin List <cygwin at cygwin dot com>
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