Hello Thomas!

Welcome to FSVS.


> So the answer to #1 is that, yes, FSVS simply uses the same backend as
> SubVersion.  Which means that I can connect it directly to our existing
> SVN repositories.
Correct, so your point #2 is answered, too.

> And some more background information from the v1.0.5 release thread,
> which might be useful to add to the FSVS site.  (This is the sort of
> information that catches my eye when I'm trying to figure out what a
> particular piece of software does.)
I'll include something like that to the overview page.
Thank you for the hint.

> Point #1 in that description raises a question... and maybe this is a
> foolish question.  How well does that play with SELinux (i.e. CentOS5)
> in enforcing mode?  (Yes, I need to read up on exactly how SELinux does
> it's magic, it's still a black box for me that is *mostly* just working.)
Well, with "mode" I meant the 07777 bits ... These should be restored.
Although I have to admit I never tested with SELinux - I don't really know
what it does, like you.


And regarding #3:
I'd use the same repository for all similar clients. Just because for a
new machine you simply do a "svn cp URL/machine1 URL/machine2", change a
few files (name, IP address) and go! Without having to copy some big
amount of data.

Furthermore you can do something like "svn diff URL/machine1 URL/machine2"
- which is not as easy with separated repositories.

And as soon as issue 2286 is done in subversion
(http://subversion.tigris.org/issues/show_bug.cgi?id=2286) it's even more
appealing to keep all machines in a single store.

> It seems like it would be better to use separate repositories
> (along with individual SSH keys for each client machine).
You can use individual keys per machine - you just have a bigger
authorized_keys.
And the rights per-machine can be restricted on a svnserver-base too, IIRC.


HTH. Please do not hesitate to bring more feedback!


Regards,

Phil


-- 
Versioning your /etc, /home or even your whole installation?
             Try fsvs (fsvs.tigris.org)!

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to