Hi Luke, for versioning adminstrative files in cvs I make a copy of all these files and add the copies to cvs. This works well, because I don't want a cvs update to overwrite the original system files. Walter -----Ursprüngliche Nachricht----- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Gesendet: Donnerstag, 13. September 2001 07:16 An: [EMAIL PROTECTED] Betreff: CVS management of /etc - permissions problem I've recently tackled a problem I've wanted to solve with CVS for a long time now - namely, managing the configuration of a Unix machine (especially desktop Linux machines), via CVS. The rationale is that if I change a system config file, and months later discover that something has stopped working, or if some install program has written over a config file without my knowledge, then it'd be great to be able to do a cvs diff and see what has changed. Should make it really easy to diagnose problems, and considerably ease the burden of system maintenance. To this end I've written a script which checks in as much or as little of /etc's text files as you want. And now I've found that CVS is getting in the way, by wiping the group and file and directory permissions of the files being added. (It doesn't change the permissions of the files you add - but the permissions etc. in the archive seem to owe more to your umask than to the file. So, for example, /etc/passwd would be readable by everybody, or /etc/profile might not be readable by anyone except root.) I've noticed the discussions about directory permissions, but none of them would solve this problem. This sounds like it would be perfect, when implemented. luke _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
