<div dir="ltr"><br><br><div class="gmail_quote">On Wed, Jun 6, 2012 at 1:34 PM, ilya <span dir="ltr"><<a href="mailto:ilya@total-knowledge.com" target="_blank">ilya@total-knowledge.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
It is generally possible, though I'd recommend making your git repo out of<br>
/etc, not /, since this is what you mostly want to track, and managing<br>
.gitignore of<br>
the whole FS will be too painful.<br>
One thing git does not track though, is file ownership. This might be a<br>
problem for<br>
some files.<br>
<div class="HOEnZb"><div class="h5"><br></div></div></blockquote><div>Git permission problem can be solve like this (Not the best, but still usable):<br><a href="http://stackoverflow.com/questions/3207728/retaining-file-permissions-with-git">http://stackoverflow.com/questions/3207728/retaining-file-permissions-with-git</a><br>
<br></div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="HOEnZb"><div class="h5">
On 06/06/12 12:57, Eli Billauer wrote:<br>
> Hi all,<br>
><br>
> I'd just like to get your input before I do something stupid. The<br>
> idea, anyhow, is to create a git repository on my system's root<br>
> directory, and add many of the system's configuration files (e.g. some<br>
> of /etc/) for tracking.<br>
><br>
> This sounds a bit bizarre even to me, but my question is: Do you see<br>
> anything bad that could happen?<br>
><br>
> I can see a few advantages:<br>
><br>
> 1. Keep track of my changes in the configuration files over time<br>
><br>
> 2. Easily spot what has changed, if something breaks for no apparent<br>
> reason (after some well-meaning automatic utility "helps me out")<br>
><br>
> 3. Possible to run a cronjob on "git commit -a", maintaining a history<br>
> of these files (and makes it easy to fall back to a known set)<br>
><br>
> 4. More freedom to hack these files to solve a problem, knowing that<br>
> the "working set" it there to fall back to.<br>
><br>
> 5. Migrating to a new computer by cloning the repository and<br>
> selectively patching the new system.<br>
><br>
> And some disadvantages:<br>
><br>
> 1. Opening a security loophole somehow (?)<br>
><br>
> 2. Possibly exposing files containing secrets (otherwise readable by<br>
> root only, e.g. /etc/ppp/pap-secrets and other password files)<br>
><br>
> 3. Running git as root<br>
><br>
> 4. Mess up the system somehow because git wasn't meant to handle<br>
> sensitive files (?)<br>
><br>
><br>
><br>
><br>
> So what do you say? A bad idea? A brilliant idea? Everyone's doing it<br>
> and nobody told me?<br>
><br>
> TAI,<br>
><br>
> Eli<br>
><br>
<br>
<br>
</div></div><div class="HOEnZb"><div class="h5">_______________________________________________<br>
Linux-il mailing list<br>
<a href="mailto:Linux-il@cs.huji.ac.il">Linux-il@cs.huji.ac.il</a><br>
<a href="http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il" target="_blank">http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il</a><br>
</div></div></blockquote></div><br></div>