X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=2.0 required=5.0 tests=AWL,BAYES_20,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By:	sourceware.org
Date:	Tue, 29 Jun 2010 13:39:07 +0200
From:	Michael Ludwig <milu71 AT gmx DOT de>
To:	cygwin AT cygwin DOT com
Subject:	Re: Moving Cygwin directory safe?
Message-ID:	<20100629113907.GI5344@wladimir>
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<20100626141016 DOT GD3672 AT wladimir> <3710255202 DOT 20100627051050 AT mtu-net DOT ru> <20100627095521 DOT GI3672 AT wladimir> <20100627133726 DOT GA5344 AT wladimir> <20100627190136 DOT GC13357 AT ednor DOT casa DOT cgf DOT cx> <20100628205722 DOT GF5344 AT wladimir> <20100629082510 DOT GX8163 AT calimero DOT vinschen DOT de>
MIME-Version:	1.0
In-Reply-To:	<20100629082510.GX8163@calimero.vinschen.de>
User-Agent:	Mutt/1.5.20 (2009-12-10)
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

Corinna Vinschen schrieb am 29.06.2010 um 10:25 (+0200):
> On Jun 28 22:57, Michael Ludwig wrote:

> Actually, while it's not necessary, it makes sense to keep the entries
> under the "installations" key intact.  They are generated the first
> time a Cygwin DLL is used.  They are useful to find out where Cygwin
> DLLs are (or were) installed on your system.  Including the 64 bit hex
> value which forms the names of the entries, it allows to diagnose
> problems which potentially arise from parallel Cygwin installations.
> If you move your installation to another path, a new entry will be
> generated.

Indeed - I now have two entries under the "Installations" key. To please
the Gods, I restored the first one to the original directory. Thanks!

> > To be complete on this issue and include one detail I omitted from
> > my list: Explorer failed to copy some files (SSH keys), which
> > belonged to the user NT-AUTORITÄT\SYSTEM and could not be read by
> > my admin user, so I had to do the following:
> > 
> >   subinacl /file C:\cygwin\etc\ssh* /setowner=michael
> >   subinacl /file C:\cygwin\etc\ssh*key /grant=michael=R
> 
> That's a fine case for either using Cygwin tools to create the new
> installation tree (cpio, for instance), or to use robocopy with the
> /B option.

Thanks once more - I didn't know about this apparently very useful tool.
Explorer keeps disappointing me by cowardly aborting long-running copy
operations on the first sign of trouble.

-- 
Michael Ludwig

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

- Raw text -