Some follow-up questions:
1) Permissions on /var/spool/fsvs
If I run FSVS as root and it creates these as:
# ls -l /var/spool/fsvs
drwxr-xr-x 3 root root 4096 Jun 3 18:40 5d
Are there permission leaks that I need to consider? For example, with
regular users on the box be able to read the contents of files that they
wouldn't normally be able to read by getting to them via the pristine
copies under /var/spool/fsvs? (That may even be a nonsensical question,
but it was one of the things I wondered about with using SVN on things
like /etc/shadow.)
2) When initializing the FSVS working area, there's no indication in the
README that you should initialize from any particular location on the
file system.
# fsvs init svn+ssh://[EMAIL PROTECTED]/path/to/repos
But when I look at the contents of the newly created
/var/spool/fsvs/*/*/* folder:
lrwxrwxrwx 1 root root 16 Jun 3 18:40 _base -> /root/fsvs-1.1.4
Looking farther, it's merely the README that is a bit abbreviated, the
"fsvs help init" screen gives better instructions and indicates that
whereever you are when you do the "init" is where FSVS will consider the
working copy to be.
3) Would the "WAA" variable be better named as "FSVS_WAA"?
4) "fsvs init" doesn't give any visual feedback to the user. Even if I
ran it twice on the same location. (The "poke it with a stick" method to
make it complain and give me some feedback?)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
