You might be interested a tool called "cfengine". Here's it's homepage:
http://www.cfengine.org/
and a nice intro article at Linux Journal (though you don't need a
network config for just 1 machine):
http://www.linuxjournal.com/article.php?sid=6848
I think when most people think about versioning config files, they are
really looking for something like cfengine - though svn will probably
work as well.
As far as permissions go in svn, it will only restore them to whatever
the current user's umask is set to. Files like /etc/shadow that are
private will probably not be restored properly.
Richard In Public wrote:
> Hi All
>
> The (inherently complex) configuration of a linux installation begs to
> be versioned. Here is what I'm planning to do:
>
> [After backing up all files to be versioned]
>
> 1. Create an empty "installation" repository
> 2. Checkout a working copy into / (i.e. / now contains .svn)
> 3. Add /etc and, for example, /opt/tomcat/conf to repository (add,
> commit)
> 4... Commit / after updating configuratons enabling rollbacks, diff,
> etc.
>
> The two issues that come to mind are:
> 1. Security - obviously the repository needs to be closely guarded
> 2. Permissions - this is only useful if svn 'remembers' the
> permissions of each file
>
> A quick test suggests that SVN does indeed restore permissions as
> checked in. So no problems?
>
> Well, I thought I'd see if anyone has tried this or forsees any
> problems with this scheme...
>
> best regards,
>
> Richard Hoberman
>
>
--
Brian Mathis
http://directedge.com/b/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Mar 3 20:35:56 2004