From: "David Härdeman" <david@hardeman.nu>
To: git@vger.kernel.org
Subject: Using git to store /etc, redux
Date: Sat, 19 May 2007 19:48:15 +0200 [thread overview]
Message-ID: <20070519174815.GA5124@hardeman.nu> (raw)
I recently had the idea to store and track /etc using git. When googling
the topic I came across the "Using git to store /etc" thread from the
end of last year which provided some interesting details on what would
be necessary.
It seems the file metadata (owner, group, mode, xattrs, etc) was the big
stumbling point, so I wrote up a tool over the last few days which
allows the metadata to be stored in a separate file which can be stored
along with the rest of the data in the repo (or separately).
This is also useful for tripwire type checks and for other types of
storage which drops some of the metadata (tar comes to mind)...
The tool (metastore) is available from:
git://git.hardeman.nu/metastore.git
Not completely cleaned up yet (it lacks a real README and some Makefile
targets) but I hope it might be useful to others (it sure is to me).
Please CC me on any replies.
--
David Härdeman
next reply other threads:[~2007-05-19 17:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-19 17:48 David Härdeman [this message]
2007-05-19 23:37 ` Using git to store /etc, redux david
2007-05-20 9:48 ` David Härdeman
2007-05-21 18:32 ` Jan Hudec
2007-05-22 12:16 ` David Härdeman
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=20070519174815.GA5124@hardeman.nu \
--to=david@hardeman.nu \
--cc=git@vger.kernel.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).