[KLUG Members] Re: RCS help

[Bob Kanaley]

Jamie,

Thanks for the response. Using CVS and a make file sounds like a slick way
to automate the maintenance of my config files. Unfortunately, I have never
used CVS or written a make file. I believe that you did a presentation on
CVS, but as usual, I couldn't get away from Elkhart in time to attend. I
believe it was about that time that Bruce posted the message about
maintaining his config files with RCS.

I expect that a bash script or make file to cover all the bases on
maintaining the config files for all my chrooted and non-chroot services
would be too complicated for me to write from scratch.

I am more of a sysadmin kinda guy than a programmer. I hack scripts together
all the time, but I use someone else's examples as much as I can. Then, I
hack around until I can get things working the way I need them.

I have had to read up on CVS for a related project and will have to give it
a try.

Bob

------Original Message------
Date: Wed,  6 Nov 2002 11:35:43 -0500
From: Jamie McCarthy <jamie@mccarthy.vg>
Subject: Re: [KLUG Members] RCS help
To: members@kalamazoolinux.org
Reply-To: members@kalamazoolinux.org

rvk@agdia.com (Bob Kanaley) writes:

> Am I missing something simple here? Are there any easy
> solutions to managing these non-shell accounts, or am I really
> asking RCS to do something it is not designed to do?

This is an "if it were me" response, so you can do it any way you
want to, and my doing it differently doesn't negate that :)

If it were me, I'd use CVS instead of RCS (it's just easier, also
more powerful and such).  I'd do my CVS checkout, file editing,
and CVS commits as a non-root user.  And I'd have a (probably
extremely simple) Makefile, so a "make install" as root would copy
the files from wherever I checked them out, to wherever they were
supposed to go, and set their ownerships and permissions and such
properly.