Thanks for the tips, all. Yes, I'm nervous about doing this sort of
thing as root, right where a mistake could do the most damage. The thing
is, I'm setting up all kinds of systems right now, and being able to
back up a revision or two when I screw up would be invaluable.
So, aside from the security issues surrounding the repository, and as
long as I get it set up correctly, does anyone see any major drawbacks
to making /etc a working copy? I haven't dug around in the private .svn
directory all that much--is there a security risk involved in having
these files in the /etc filesystem?
A couple other questions and comments below.
Scott Lamb wrote:
> John Locke wrote:
>
>> Okay. I'm trying to figure out the best way to manage configuration
>> files in a couple of Linux servers. I'd like to be able to roll back
>> configuration changes if I do something that breaks the configuration.
>
>
> 3. Set up symlinks. Most stuff should follow them happily.
Not sure what you mean here--you mean replace the real files in /etc
with symlinks to a wc in /root? Or vice versa?
> You have to be a bit careful with how you manage the permissions and
> how you commit as root. Cut'n'pasted from an earlier email of mine on
> this subject:
>
>
> You can use ra_dav...but not if you want the Apache config files in
> there, because if you screw them up, you can't just "svn up" to get a
> fresh version.
... but you can svn revert httpd.conf... how many times would that have
been handy!
Finally, Dan Mercer dropped me a line about a Collab.net project for
managing Linux/Solaris configurations that sounds intriguing.
Cheers,
John Locke
Owner, Freelock, LLC
Small Business Computing with Open Source
http://www.freelock.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Aug 14 00:03:16 2003