From: sirjofri <sirjofri+ml-9front@sirjofri.de>
To: 9front@9front.org
Subject: Re: [9front] Free Carrots #4: Making Backups
Date: Mon, 25 Apr 2022 10:31:12 +0000 (UTC) [thread overview]
Message-ID: <202e9c1d-00ab-45cf-8bf3-943651b68e47@sirjofri.de> (raw)
In-Reply-To: <d8501e378110871e4c7aa85bba182f2d@a-b.xyz>
Hey all,
I addition to mkfs, I played around with replica some time ago for the
exact same reason. I wrote a little blog post about it here:
https://sirjofri.de/changeblog/1593621046/
The linked files aren't in that location anymore, but here instead:
https://sirjofri.de/oat/rc/guidedreplica/
Disclaimer: the solution is very buggy for a common push/pull scenario I
intended it back then (syncing files to a laptop and be able to sync them
back, but only changed files). Use with care and make proper backups!
See also: replica(1), replica(8)
sirjofri
next prev parent reply other threads:[~2022-04-25 10:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-23 4:22 Stanley Lieber
2022-04-25 6:21 ` igor
2022-04-25 7:37 ` kvik
2022-04-25 10:31 ` sirjofri [this message]
2022-04-25 10:39 ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2022-04-25 12:32 ` hiro
2022-04-26 11:42 ` qwx
2022-04-26 14:23 ` Steve Simon
2022-04-27 23:30 ` sl
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=202e9c1d-00ab-45cf-8bf3-943651b68e47@sirjofri.de \
--to=sirjofri+ml-9front@sirjofri.de \
--cc=9front@9front.org \
/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 NNTP newsgroup(s).