On 01/03/2007, at 4:26 AM, David Robillard wrote:
Well, I'm not quite sure that it will answer all of your questions,
but take a look at Luke Kanies's article called ''Using version
control in system administration''.
It's available from the USENIX website at
On 2/27/07, Rob [EMAIL PROTECTED] wrote:
David Chuck,
I'm already using RCS, and I've built a somewhat clunky mechanism
around it.
One machine holds the master copies of
- site-wide files (/etc/ntp.conf, /etc/resolv.conf, /etc/syslog.conf)
- host-specific files (/etc/hosts, /etc/passwd,
On 27/02/2007, at 5:16 AM, David Robillard wrote:
If you simply want to track changes and be able to roll back your
configuration files, then go with a more simple approach like using
RCS locally. RCS is part of the base FreeBSD system.
David Chuck,
I'm already using RCS, and I've built a
Rob wrote:
I'd like some advice on managing config files on multiple servers with a
source control system. The idea is to update files locally, and commit
them back to a central repository.
I know that CVS is the usual choice, but there are a couple of things
that I can't get CVS to do.
[
If you don't have strong ties to CVS, already, I suggest using Subversion. It
handles many of your complaints about permissions and symlinks better than CVS
does.
I agree, Subversion is better then CVS. We've switched from CVS to
Subversion a year ago and so far the entire dev team is very
On 2007-02-26 07:01, Rob [EMAIL PROTECTED] wrote:
Dear List,
I'd like some advice on managing config files on multiple servers
with a source control system. The idea is to update files locally,
and commit them back to a central repository.
I know that CVS is the usual choice, but
