From: jidanni@jidanni•org
To: git@vger•kernel.org
Cc: etckeeper@packages•debian.org
Subject: sneakernet everyday recommendations?
Date: Fri, 19 Dec 2008 10:33:06 +0800 [thread overview]
Message-ID: <877i5whp25.fsf@jidanni.org> (raw)
Say, on a sneakernet what would you use for
A>B A<B A>B... updating? git-commit and git-bundle and git-merge?
You see I have the two computers, that I use on alternating days, a
sort of redundancy strategy.
Normally if I change my .bashrc or /etc/ppp/ip-up.d/bla, etc. I just
cpio -o it to a CF card, the common sneakernet junction between my two
systems that are never powered up at the same time. And then cpio -i
it to the other system the following day.
To use git instead, On each computer I shall have my shutdown script
ask me about a commit, and my boot script ask me about a merge.
To track metadata, I will employ etckeeper.
I don't want to track the entire machines, just 100 or so files, which
I have git-added.
(Hmmm, also copying /var/cache/debconf/config.dat and
/var/lib/aptitude/pkgstates to the CF card
should be enough to complete my minimal restoreability strategy
in contrast to the many more bulkier 'system snapshot' solutions out there).
reply other threads:[~2008-12-19 2:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=877i5whp25.fsf@jidanni.org \
--to=jidanni@jidanni$(echo .)org \
--cc=etckeeper@packages$(echo .)debian.org \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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