X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
Date:	Tue, 29 Jun 2010 10:25:10 +0200
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Moving Cygwin directory safe?
Message-ID:	<20100629082510.GX8163@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
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>
MIME-Version:	1.0
In-Reply-To:	<20100628205722.GF5344@wladimir>
User-Agent:	Mutt/1.5.20 (2009-06-14)
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

On Jun 28 22:57, Michael Ludwig wrote:
> Christopher Faylor schrieb am 27.06.2010 um 15:01 (-0400):
> > On Sun, Jun 27, 2010 at 03:37:26PM +0200, Michael Ludwig wrote:
> 
> > >I copied C:\cygwin to T: instead of reinstalling. Here's a list of
> > >things I had to fix (or fixed preemptively):
> > >
> > >* fixed the above registry settings
> > 
> > ...which was not necessary.
> 
> Yes, you hinted at that it might not be, but I didn't know whether these
> keys are left-overs from by-gone versions, or derived from some other
> setting, or whatnot, so not knowing whether I could delete them I
> thought I might as well adapt them to reflect the new values,

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.

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


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

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