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

Re: Large-scale configuration backup with GIT?

From
David Kastrup <dak@gnu.org>
Date
Sep 2, 2007, 20:37 UTC
Message-ID
<85642spzvs.fsf@lola.goethe.zz>
In-Reply-To
<20070902201724.GB10567@lug-owl.de>
Jan-Benedict Glaw <jbglaw@lug-owl.de> writes:
Show 13 quoted lines
> I'm just thinking about storing our whole company's configuration into
> GIT, because I'm all too used to it. That is, there are configuration
> dumps of n*10000 routers and switches, as well as "regular"
> configuration files on server machines (mostly Linux and Solaris.)
> While probably all of the server machines could run GIT natively, we
> already have some scripts to dump all router's/switch's configuration
> to a Solaris system, so we could it import/commit from there. There
> might be a small number of Windows machines, but I guess these will be
> done by exporting the interesting stuff to Linux/Solaris machines...
>
> I initially thought about running a git-init-db on each machine's root
> directory and adding all interesting files, but that might hurt GIT's
> usage for single software projects on those machines, no?

It could break shell scripts, since cd /;echo `pwd`/filename does not return /filename.

I don't think that the root directory is a good place for starting git.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum
Previous: Jan-Benedict GlawNext: Jan-Benedict Glaw
Message 2 of 5 in “Large-scale configuration backup with GIT?”
  1. Jan-Benedict GlawSep 2, 2007
  2. David KastrupSep 2, 2007
  3. Jan-Benedict GlawSep 2, 2007
  4. Junio C HamanoSep 2, 2007
  5. Martin LanghoffSep 3, 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.