[3054] in SIPB-AFS-requests
Re: Proceeding with new-rosebud
daemon@ATHENA.MIT.EDU (Greg Hudson)
Mon Jul 13 11:19:55 1998
To: mhpower@MIT.EDU
Cc: jhawk@MIT.EDU, sipb-afsreq@MIT.EDU
In-Reply-To: Your message of "Mon, 13 Jul 1998 03:13:14 EDT."
<9807130713.AA09540@yaz-pistachio.MIT.EDU>
Date: Mon, 13 Jul 1998 11:19:45 EDT
From: Greg Hudson <ghudson@MIT.EDU>
> And I believe we also want to avoid the situation where the
> machine's configuration is encapsulated in an epic poem that is
> passed down through generations of sipb members via an oral
> tradition.
I agree that SIPB doesn't want little configuration changes to involve
a lot of voodoo (like editing mkserv scripts), and I think the two
ways we have of keeping track of configuration files(*) are both fine.
I think mainly what we're missing is a way of figuring out what
software (stuff under /afs/sipb/service) and OS patches are installed
on a machine. It's probably sufficient to instate a file under
/afs/sipb/machine/servername which gives that information.
(*) For reference, the two ways are, roughly: (1) keep a tree of
modified configuration files under RCS in
/afs/sipb/machine/servername, and (2) nightly backups of a preset list
of configuration files into some place in AFS. The first gives us a
version history; the second is less work and guaranteed to remain in
sync.
