Re: using cvs to contol system files
woods-at-weird.com (Greg A. Woods) |info-cvs| wrote: [ On Wednesday, October 23, 2002 at 17:38:05 (-0500), Miller Dale Contractor HQ AFWA wrote: ] Subject: RE: using cvs to contol system files We use CVS for controlling our software but for the system files I find that RCS is generally sufficient. RCS is simple to use and gives you version control with few commands to know. I concur 100% I have in the past devised procedures and processes to use CVS to manage system configurations (which ended up having to be much more complex than vi1pdqyo02 was proposing), but I would not do so ever again without using something like GNU Cfengine to do the work and then just use CVS to manage the cfengine inputs. -- Greg A. Woods +1 416 218-0098;[EMAIL PROTECTED]; [EMAIL PROTECTED] Planix, Inc. [EMAIL PROTECTED]; VE3TCP; Secrets of the Weird [EMAIL PROTECTED] I'll be looking into GNU Cfengine. This could be a better long term solution for my admins. Thankyou ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
erasing history
Suppose I was experimenting with a few cvs features and later wanted to delete any record of my checkins and updates etc. Is there any reason why it would be a bad idea to delete the offending lines from $CVSROOT/CVSROOT/history? I was going to also delete any directories I created in the repository and changes in the sandboxDir/CVS/Entries file as well. Is this everything? Is there a better way? Thanks for any help. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
using cvs to contol system files
Has anyone out there used to cvs to version control system files? For instance, files in /etc. I'm working with 2 system admins who want to do this. We were going to make the 'live' files a sandbox that they would share. I was hoping to have them edit files by logging in to their regular accounts, su to root, edit a file, exit su, cvs commit filename. The problem is the permissions involved. They each have a umask of 022 on regular accounts. So a 'cvs add dirName' creates a directory in the repository without group write. No problem, we'll set this one by hand. The CVS/Entries file however is left as owned by the last user to commit and without a group write. This is a problem for the next admin to commit. Is there a way around this. Setting the umask in the admins regular accounts to 002 seems like a poor option. Just getting started on this problem. Any advice is appreciated. -- Protect yourself from spam, use http://sneakemail.com ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
