X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=y3pjsB+3GMZp1TiJ
	wBBJwb2WbIwjw5bHQbYiTrRexEBKQDBmHFdWHor1PNVhMxnNFk1YwGmVwhpwS+H1
	Rm0z1fjW/oM2kuxnR3Jax0Hs2gjYYh0zLpFVAqBxRmR6GgACXnWVYVhe0k1rhKsg
	z1WvmR3dP+A+BnSkCK1ZeXBdo+Y=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; s=default; bh=VocKTQrOM49H+gxCoZn0ff
	QkGV8=; b=l4hTgXJc9lgO2RMEstfbxezImzud9PfLe7qEoH4A62MY7Rbc8BPvMD
	Mn9Gdd+vNjt+zzYQFr+6jyBixVqk4qw+d0214fA7lirJBo0O2A5KZz9f6BW19RBZ
	ltnleBz9DqQ5viM1S0e+LWyFRfF/4GQvg/hRSEkVts8FeMFnsdztk=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.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
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-3.3 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,KAM_THEBAT,SPF_SOFTFAIL autolearn=no version=3.3.2
X-HELO:	smtp.ht-systems.ru
Date:	Sat, 4 Apr 2015 21:52:18 +0300
From:	Andrey Repin <anrdaemon AT yandex DOT ru>
Reply-To:	cygwin AT cygwin DOT com
Message-ID:	<9784082.20150404215218@yandex.ru>
To:	Eric Pement <eric DOT pement AT gmail DOT com>, cygwin AT cygwin DOT com
Subject:	Re: Can I move Cygwin and Cygwin64 to a drive other than C: ?
In-Reply-To:	<CAB+hQJ7DxJ6Qye4r395Dpu+emBxnyQeZvXa56yv+iwr3UsDH=A@mail.gmail.com>
References:	<mfga42$ee7$1 AT ger DOT gmane DOT org> <20150401084752 DOT GN13285 AT calimero DOT vinschen DOT de> <mfilln$eq0$1 AT ger DOT gmane DOT org> <20150402081749 DOT GF13285 AT calimero DOT vinschen DOT de> <CAB+hQJ7DxJ6Qye4r395Dpu+emBxnyQeZvXa56yv+iwr3UsDH=A AT mail DOT gmail DOT com>
MIME-Version:	1.0
X-IsSubscribed:	yes

Greetings, Eric Pement!

> Follow-up question for Corinna or anyone who might know the answer:

>> >On Apr  1 03:26, Robert Miles wrote:
>> > >>Can I move the entire Cygwin and Cygwin64 directory trees to one
>> > >>of the nearly empty drives, without losing the extra packages I've
>> > >>already downloaded and the files I've created?
>> > >
>> > >Robocopy allows to copy an entire Cygwin tree while keeping all
>> > >permissions intact.  I had good luck with something along the
>> > >lines of
>> > >
>> > >   robocopy C:\cygwin64 D:\cygwin64 /e /purge /z /copyall /sl
> . . .
> With an added comment that
>> I *did* move Cygwin installations using
>> robocopy and the above works for me.  In an elevated shell.

> I recently needed to move a Cygwin installation, about 6 GB, to
> another drive accessible only on a network file system. Due to the
> number of files, copying everything would have taken a week or more,
> because everything slows down when the number of files increases.

> The solution I ultimately took was not the best. I compressed
> everything into a single *.7z (7-zip) archive, moved the single
> archive across the network, and uncompressed the *.7z archive on the
> target machine.

> Although the total time was much, much faster (maybe 5 or 6 hours,
> including 30 minutes to uncompress the archive), all my file
> permissions were set to the same value, regardless of what they had
> been previously, and any extended attributes were lost entirely.

> I didn't like it, but I had no realistic alternative.

> For future resource, what is the best way to archive a Cygwin
> installation into a single file, which will preserve all file
> properties and permissions, so that the archive can be transferred to
> another location? (For the sake of clarity, presume that Cygwin does
> NOT exist in the target location, so a non-Cygwin tool must be used to
> expand the archive.)

About any sane modern archiving tool can read TAR archives.
And most of them understand gz/xz/bz2 compression.
You could have used any of that to unpack Cygwin to get a bootstrap
environment, then use that environment to unpack the tar with all permisisons
restored.
Alternatively, RAR can add/restore access data.


-- 
With best regards,
Andrey Repin
Saturday, April 4, 2015 21:48:51

Sorry for my terrible english...


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