public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "KARL BOTTS" <kdbotts@usa.net>
To: <cygwin@cygwin.com>
Subject: Re: tar cygwin64/ from old to new computer?
Date: Mon, 26 Nov 2018 13:47:00 -0000	[thread overview]
Message-ID: <252wkZNt60016Set.1543240017@web07.cms.usa.net> (raw)
In-Reply-To: <87efb8lxtt.fsf@Rainer.invalid>


This may not be strictly supported, but I have been doing it for at least 10
years:

Once I have a new host network accessible from the old, I simply copy
c:/cygwin from old to new.
Access can be via UNC, mapped drive, whatever.  I normally use 'cp -a' to do
the copy, but have done it other ways.  (Do not use Win copy commands, they
mess up links.)

Then I set a few envars (by hand, via dialog box) on the new: add c:/cygwin to
the PATH, set HOME and CYGWIN.  I keep a home dir in cloud svn, shared across
all machines, to which HOME points, which I check out onto the new, by remote.
 Make a couple shortcuts to start bash, mintty, like that.

And up she comes.  I have a file of notes to follow, but really, the above is
about it.

Thereafter, I run CygSetup on one machine, make sure I like it, then just copy
c:/cygwin to the other machines again.  (Of course, copy it first, then rename
it on the dest with a DOS command, with cygwin shut down.)  I do that about
once a year.  I have about 6 active machines -- home, work, Acure -- and this
keeps them all in sync.

Compared to Visual Studio and ilk, maintaining cygwin is a breeze this way.


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

  reply	other threads:[~2018-11-26 13:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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=252wkZNt60016Set.1543240017@web07.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).