public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Russell VT <russellvt@gmail.com>
To: Vanda Vodkamilkevich <vanda.vodkamilkevich@gmail.com>
Cc: cygwin@cygwin.com
Subject: Re: Switch to a new PC
Date: Fri, 4 Feb 2022 02:26:55 -0800	[thread overview]
Message-ID: <CANV2+nXEFQYQw5FU1M-mqQnFCk28_nWYRg0fwm5VAm-EN6yWxw@mail.gmail.com> (raw)
In-Reply-To: <CA+GYywCd49GJLAGYJrKbwizZxAW+LwLB0S9SpieqwRyEikVEVw@mail.gmail.com>

This is "a religious" question, as there are many different "sworn" ways to
do it.

The "old reliable" method, if you have both filesystems available... at
least off the top of my head...

cd / ; tar -cvf - / | (cd /path/to/other/disk ; tar -xvfp -)


There are also many other solutions using things like cpio and dd... and
technically, you can probably even do a "cp -pr /source /dest" or similar.
There are also better "purist" methods using setup to save the current list
of packages, and then pipe that to a new setup to install those same
packages, all from the command line (it's probably "the best," but you'll
have to reconfigure everything, too)

Hope that gives you a few different starting points to play with...

R VT



On Fri, Feb 4, 2022 at 2:10 AM Vanda Vodkamilkevich <
vanda.vodkamilkevich@gmail.com> wrote:

> Hi guys,
>
> Probably a known issue (I remember on this list some trick using the
> installed.db file) but I want to backup my whole cygwin tree (on a network
> drive) before switching PC and without losing anything... What is the best
> method / tool?
> (currently trying with FreeFileSync but it is excluding files in a strange
> way...)
>
> --
> Problem reports:      https://cygwin.com/problems.html
> FAQ:                  https://cygwin.com/faq/
> Documentation:        https://cygwin.com/docs.html
> Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple
>


-- 
Russell M. Van Tassell <russellvt@gmail.com>

  reply	other threads:[~2022-02-04 10:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-04 10:09 Vanda Vodkamilkevich
2022-02-04 10:26 ` Russell VT [this message]
2022-02-04 10:52   ` Thomas Wolff
2022-02-04 12:11     ` marco atzeri
2022-02-09 15:12       ` Vanda Vodkamilkevich
2022-02-09 18:05         ` Adam Dinwoodie
2022-02-10 13:53           ` Jon Turney
2022-02-10 14:41             ` Vanda Vodkamilkevich
2022-02-04 17:15   ` Brian Inglis

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=CANV2+nXEFQYQw5FU1M-mqQnFCk28_nWYRg0fwm5VAm-EN6yWxw@mail.gmail.com \
    --to=russellvt@gmail.com \
    --cc=cygwin@cygwin.com \
    --cc=vanda.vodkamilkevich@gmail.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).