I thing this is a newbie question?
I want use subversion (svn) to maintain host configuration files
(e.g. /etc/hosts) under a perspective of change management to
track the changes in this files.
If I put this files under version control and check-in them after a
modification, I can use the logging as documentation, fine. I know who
implement this with svn.
But in my example scenario:
- several unix host (e.g: 10)
- each system has the same /etc/nsswich.conf
I want to share this file over all system and use svn as rollout tool
(Modify, check-in, check-out on all hosts)
- each system has an individual /etc/hosts
Every file from every system should be under control.
I was able to implement this scenario with svn in the
following directory structure:
/etc/hosts (a master example)
To setup the workcopy (wc), I have done the following logical steps:
1.) svn checkout .../common to /etc (wc)
2.) svn copy .../common/etc/hosts .../specific/hostA/etc/hosts
3.) svn switch /etc/hosts .../specific/hostA/etc/hosts
4.) Edit /etc/hosts, check-in, check-out works fine, this changes has
only influence to this host
5.) Edit /etc/nsswitch.conf, check-in, check-out on other hosts reflect
the change on every host, fine.
(Sorry, I have done all this steps with TortoiseSVN, so the list above
a logical sequence and hope this reflect my steps).
My main questions:
- Is this a good way to implement my requirement.
It's a complex setup and I need a concept who to organize the
- Has somebody a better/easier way/idea to implement the scenario
- If I loose the svn meta-directory (.svn), I must know, that I
first have to checkout the common tree and than "overlay" the
specific host with it's specific changes from specific directory.
I think this is easy to script, if the concept about the
respository organization is done
Thanks for reading this and I hope you can understand my question.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Fri Sep 16 13:18:18 2005