Jan-Benedict Glaw <jbglaw@xxxxxxxxxx> writes: > 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 - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
