Andy, > Why don't you create a subdirectory that you checkout > everything into. > ... > Then from your home directory create symlinks into the subdirectory. Or just move the CVS directory. Here's a script I use to add files to my repository. I use it (as root) to maintain my OS config files: httpd.conf, namd.conf, ... > Greg A. Woods wrote: > ... > Don't use CVS with the superuser account. > ... > If you really think you must try to use CVS to manage system > configuration files (which is, I've learned the hard way, not really a > good idea unless you also use something very sophisticated to validate > and install those files, such as GNU cfengine), then you should do all What was hard about it Greg? I've been using CVS to manage system configuration files for two years now. I use a unique repository that only root can read/write. The only draw back is that I have CVS directories all over my OS. I use Red Hat 6.2 Linux 2.2.14-5.0 and CVS 1.10.7. Kalle Hoffman [EMAIL PROTECTED] http://www.kalle.com
#!/bin/sh ######################################################################## # Kalle Hoffman # Thu Aug 3 15:15:50 2000 # [EMAIL PROTECTED] # http://www.kalle.com ######################################################################## ######################################################################## # execute a command and exit if it fails ######################################################################## doit() { #echo doit: $* eval $* if [ ! $? = 0 ] then #echo "cvsinit: command FAILED: $*" exit 1 fi } umask 002 doit mkdir -p $CVSROOT/`pwd` doit mkdir -p CVS chmod 2775 $CVSROOT/`pwd` CVS if [ ! -f CVS/Repository ] then doit touch CVS/Entries fi if [ ! -f CVS/Repository ] then doit 'echo "$CVSROOT`pwd`" > CVS/Repository' fi if [ ! -f CVS/Root ] then doit 'echo "$CVSROOT" > CVS/Root' fi if [ -n "$*" ] then doit cvs add $* doit cvs commit -m '"initial checkin"' $* fi exit 0
