From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 105915 invoked by alias); 26 Nov 2018 13:47:04 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 105902 invoked by uid 89); 26 Nov 2018 13:47:04 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-4.9 required=5.0 tests=BAYES_50,GIT_PATCH_2,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=H*M:usa, shut, HOME, ilk X-HELO: co03.mbox.net Received: from co03.mbox.net (HELO co03.mbox.net) (165.212.64.33) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 26 Nov 2018 13:47:02 +0000 Received: from co03.mbox.net (localhost [127.0.0.1]) by co03.mbox.net (Postfix) with ESMTP id 433Srh65vKzq2SS for ; Mon, 26 Nov 2018 13:47:00 +0000 (UTC) X-USANET-Received: from co03.mbox.net [127.0.0.1] by co03.mbox.net via mtad (C8.MAIN.4.17E) with ESMTP id 263wkZNU66176M03; Mon, 26 Nov 2018 13:46:57 -0000 X-USANET-Routed: 3 gwsout-vs Q:bmvirus X-USANET-Routed: 3 gwsout-vs Q:bmvirus X-USANET-GWS2-Tenant: usa.net X-USANET-GWS2-Tagid: UNKN Received: from ca31.cms.usa.net [165.212.11.131] by co03.mbox.net via smtad (C8.MAIN.4.17D) with ESMTP id XID030wkZNU66040X03; Mon, 26 Nov 2018 13:46:57 -0000 X-USANET-Source: 165.212.11.131 OUT kdbotts@usa.net ca31.cms.usa.net CLR X-USANET-MsgId: XID030wkZNU66040X03 Received: from web07.cms.usa.net [165.212.8.207] by ca31.cms.usa.net (ESMTP/kdbotts@usa.net) via mtad (C8.MAIN.4.10M) with ESMTP id 562wkZNU61472M31; Mon, 26 Nov 2018 13:46:57 -0000 X-USANET-Auth: 165.212.8.207 AUTO kdbotts@usa.net web07.cms.usa.net CLR Received: from 73.247.78.3 [73.247.78.3] by web07.cms.usa.net (USANET web-mailer C8.MAIN.4.16Q); Mon, 26 Nov 2018 13:46:57 -0000 Date: Mon, 26 Nov 2018 13:47:00 -0000 From: "KARL BOTTS" To: Subject: Re: tar cygwin64/ from old to new computer? Mime-Version: 1.0 Message-ID: <252wkZNt60016Set.1543240017@web07.cms.usa.net> References: <20181125143854.GA20164@ingber.com> <20181125193110.GA18332@ingber.com> <87efb8lxtt.fsf@Rainer.invalid> In-Reply-To: <87efb8lxtt.fsf@Rainer.invalid> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Z-USANET-MsgId: XID562wkZNU61472X31 X-IsSubscribed: yes X-SW-Source: 2018-11/txt/msg00184.txt.bz2 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 acro= ss all machines, to which HOME points, which I check out onto the new, by remo= te. 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 c= opy c:/cygwin to the other machines again. (Of course, copy it first, then ren= ame 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 th= is 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