From: L A Walsh <cygwin@tlinx.org>
To: cygwin@cygwin.com
Subject: Re: tar cygwin64/ from old to new computer:
Date: Mon, 26 Nov 2018 19:19:00 -0000 [thread overview]
Message-ID: <5BFC4751.501@tlinx.org> (raw)
In-Reply-To: <1381677255.20181125225824@yandex.ru>
On 11/25/2018 11:58 AM, Andrey Repin wrote:
> Greetings, L A Walsh!
>> ---
>> Hmm...can't tar it, but he could drag&drop from Explorer
>> like he was moving the image (but do a copy instead).
>
> It would screw permissions on Cygwin files/directories.
---
Perhaps, I haven't tried this particular use case,
however, usually it just duplicates them.
Think about the local case. There it just does a rename.
I don't think they would deliberately allow custom ACL's to be tossed
just because the copy was to a different device.
But, once you had the files in place, wouldn't an rsync
from old to new, fix up just the ACL's?
If rsync won't work, then use "cp":
> cp -rd --attributes-only /old /new
Is there a reason why that wouldn't (or shouldn't)
work?
--
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
next prev parent reply other threads:[~2018-11-26 19:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-25 14:39 tar cygwin64/ from old to new computer? Lester Ingber
2018-11-25 17:09 ` Hans-Bernhard Bröker
2018-11-25 19:22 ` tar cygwin64/ from old to new computer: L A Walsh
2018-11-25 20:05 ` Andrey Repin
2018-11-26 19:19 ` L A Walsh [this message]
2018-11-25 17:20 ` tar cygwin64/ from old to new computer? Achim Gratz
2018-11-25 18:50 ` Andrey Repin
2018-11-25 19:31 ` Lester Ingber
2018-11-25 20:13 ` Achim Gratz
2018-11-26 13:47 ` KARL BOTTS
2018-11-26 20:32 Gilbert St. Firmin
2018-11-26 21:22 ` Hans-Bernhard Bröker
2018-11-27 15:20 ` Andrey Repin
2018-11-27 15:34 ` cyg Simple
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5BFC4751.501@tlinx.org \
--to=cygwin@tlinx.org \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).