X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:to:subject:mime-version:message-id :references:in-reply-to:content-type:content-transfer-encoding; q=dns; s=default; b=CF8QtaB8EW39J0l61kGtlUJAdq+8EfbiXOPewqxGKs7 Fr1lUKscNYKZ0SJ6CwRD4I5B+4RU4DFX0MsZdRHweZ40lKnzbX2yTeIj9A22aCRi xLJjw7z2sALc48Fr7aiFnvHSL1Y5U4L9jFY17gmlDMfdWqigOuGEChQftHJYRGc4 = DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:to:subject:mime-version:message-id :references:in-reply-to:content-type:content-transfer-encoding; s=default; bh=Ic7NjFPSvQhOb0HQAGUeX3PjNpc=; b=lGqaMVodcU3vmjnJT wDvG4XLxT3PGVn/K+Y4SyN7pMf5adIg8OyTyCJ1+lhwoz4SiJSWYf995/KyhzC4z zA3373+YGEQrlF7ZLGsLCB5+JHaFldzVTQHcgB5z/zL6Zy21zQvk0+Jj7iDGPXMS Y41DXYjBtVg5rTq52AIHI1B9Oo= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com 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 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 X-USANET-Source: 165.212.11.131 OUT kdbotts AT usa DOT net ca31.cms.usa.net CLR X-USANET-MsgId: XID030wkZNU66040X03 X-USANET-Auth: 165.212.8.207 AUTO kdbotts AT usa DOT net web07.cms.usa.net CLR Date: Mon, 26 Nov 2018 07:46:57 -0600 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 DOT GA20164 AT ingber DOT com> <20181125193110 DOT GA18332 AT ingber DOT com> <87efb8lxtt DOT fsf AT Rainer DOT invalid> In-Reply-To: <87efb8lxtt.fsf@Rainer.invalid> Content-Type: text/plain; charset=ISO-8859-1 Z-USANET-MsgId: XID562wkZNU61472X31 X-IsSubscribed: yes Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id wAQDlDsB017676 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 AT usa DOT 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