From: "Hans-Bernhard Bröker" <HBBroeker@t-online.de>
To: cygwin@cygwin.com
Subject: Re: tar cygwin64/ from old to new computer?
Date: Mon, 26 Nov 2018 21:22:00 -0000 [thread overview]
Message-ID: <1ef634d1-5ace-88ba-4869-85597adb5b7f@t-online.de> (raw)
In-Reply-To: <CAHCVaW6a5sO=F+9DJc+WiebeU9CEUfBXuYxnfX_oUf1e4hZosQ@mail.gmail.com>
Am 26.11.2018 um 21:32 schrieb Gilbert St. Firmin:
> Could the native Windows version of 7-zip be used on both old and new
> computers?
Possibly. If that can be taught to copy all the attributes used by
Cygwin, without running into the usual problems we see whenever Windows
tools are used to handle those. But I really very much doubt it. This
really is a full blown chicken-and-egg situation: the only tools really
known to be able to correctly copy Cygwin files including all their ACLs
are Cygwin itself, and its installer. All other tools are suspect.
It all comes back down to what I wrote in my initial answer: is remote
access to a Cygwin mirror server really so much slower than your local
network that there's even any gain to be had from going this untested
route? I.e. why even risk this?
--
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 21:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-26 20:32 Gilbert St. Firmin
2018-11-26 21:22 ` Hans-Bernhard Bröker [this message]
2018-11-27 15:20 ` Andrey Repin
2018-11-27 15:34 ` cyg Simple
-- strict thread matches above, loose matches on Subject: below --
2018-11-25 14:39 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
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
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=1ef634d1-5ace-88ba-4869-85597adb5b7f@t-online.de \
--to=hbbroeker@t-online.de \
--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).