git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Using git to store /etc, redux

From
JHJan Hudec <bulb@ucw.cz>
Date
May 21, 2007, 18:32 UTC
Message-ID
<20070521183239.GB5082@efreet.light.src>
In-Reply-To
<20070519174815.GA5124@hardeman.nu>
On Sat, May 19, 2007 at 19:48:15 +0200, David Härdeman wrote:
Show 20 quoted lines
> 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.

Have you looked at IsiSetup (http://www.isisetup.ch/, linked from http://git.or.cz/gitwiki/InterfacesFrontendsAndTools) yet? It's a front-end to git specifically targeted for versioning configuration. From a quick glance at it's web I don't see whether it already stores the metadata you describe, but in either case it could be interesting for you.

-- 
						 Jan 'Bulb' Hudec <bulb@ucw.cz>
Previous: David HärdemanNext: David Härdeman
Message 4 of 5 in “Using git to store /etc, redux”
  1. David HärdemanMay 19, 2007
  2. david@lang.hmMay 19, 2007
  3. David HärdemanMay 20, 2007
  4. Jan HudecMay 21, 2007
  5. David HärdemanMay 22, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.