From: "KARL BOTTS" <kdbotts@usa.net>
To: "cygwin" <cygwin@cygwin.com>
Subject: Re: Is there a way to clone-install Cygwin?
Date: Fri, 31 Jan 2020 14:06:00 -0000 [thread overview]
Message-ID: <424yaEoFi7856Set.1580479568@web03.cms.usa.net> (raw)
>>> Cygwin is totally portable! You can simply copy the installation folder
to
>>> another PC, copy the shortcut (edit target if needed) and it will work.
>> How do you copy it?
>> Which archive container do you use?
I have been using this approach for years.
To a new naked Windows box, if you can "mount" it over the network, e.g., map
a drive letter to it, then you can use cygwin tools from an existing box with
cygwin, to copy cygwin to the new. I usually use cygwin tar, but I think 'cp
-a' will work. I think in the past, I have used robocopy. The key is the
links and symlinks: normal Windows tools won't get them right.
For upgrades, once cygwin is on both boxes, I always use tar. I've got this
down to pretty much routine. I do it once or twice a year. I upgrade cygwin
on one box, vet it for a few days, then upgrade several others. I untar into
an empty dir, then use native cmd.exe 'move' to swap the dirs.
Be sure to use 64-bit cygwin. The 32-bit used to work, but now and then I
would have to fuss with "rebase". I have never had that problem with the
64-bit.
---
Karl Botts, kdbotts@usa.net
--
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 reply other threads:[~2020-01-31 14:06 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-31 14:06 KARL BOTTS [this message]
2020-01-31 14:13 ` Ulli Horlacher
2020-01-31 19:21 ` Achim Gratz
2020-01-31 20:25 ` Brian Inglis
-- strict thread matches above, loose matches on Subject: below --
2020-01-21 19:17 Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin
2020-01-21 0:58 Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin
2020-01-21 1:27 ` Brent Epp
2020-01-31 10:25 ` Ulli Horlacher
2020-01-31 11:29 ` Ulli Horlacher
2020-01-31 12:05 ` Ulli Horlacher
2020-01-31 12:54 ` Thomas Wolff
2020-01-31 14:06 ` Ulli Horlacher
2020-02-01 10:05 ` Andrey Repin
2020-02-01 11:21 ` BGINFO4X
2020-02-03 16:40 ` Ulli Horlacher
2020-02-03 17:01 ` BGINFO4X
2020-02-04 17:16 ` Ulli Horlacher
[not found] ` <16fc5b08e80.2780.a1382e26d1292f71ec6ef0cd03d49346@pdc.ca>
2020-01-21 2:33 ` Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin
2020-01-21 2:55 ` Brent Epp
2020-01-21 4:46 ` Marco Atzeri
2020-01-21 20:33 ` Achim Gratz
2020-01-28 21:35 ` Andrey Repin
2020-01-28 22:00 ` Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin
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=424yaEoFi7856Set.1580479568@web03.cms.usa.net \
--to=kdbotts@usa.net \
--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).