[2044] in Release_7.7_team
re: contents of athena-base package
daemon@ATHENA.MIT.EDU (oliver thomas)
Wed Jan 12 11:07:36 2000
Message-Id: <200001121607.LAA494544@mufasa.mit.edu>
to: Jonathon Weiss <jweiss@MIT.EDU>
cc: tb@MIT.EDU (Thomas Bushnell, BSG), Greg Hudson <ghudson@MIT.EDU>,
BSG@MIT.EDU, release-team@MIT.EDU, source-developers@MIT.EDU
Cc: oliver thomas <othomas@MIT.EDU>
Reply-To: oliver thomas <othomas@MIT.EDU>
In-Reply-To: your message of Wed, 12 Jan 2000 01:19:02 -0500.
<200001120619.BAA18218@speaker-for-the-dead.mit.edu>
Date: Wed, 12 Jan 2000 11:07:24 -0500
From: oliver thomas <othomas@MIT.EDU>
> Teh idea of splitting them into seperate files per variable makes
> sense, however, those files shouldn't need to be scripts, and should
> all be in one place, so it doesn't get too much harder to edit a bunch
> of them. We should consider asking the support folks whether a change
> of this nature is likely to cause them a problem.
well, as far as athena consulting goes the change would not be a big
problem. ten minutes at a training meeting and fixing a few stock answers
should be all that's required. i imagine updating the private workstation
owner's guide will be the larger effort.
let me just make sure i grok the proposed changes: the plan is to move
rc.conf variables to individual files, one for each variable, all in a
single directory (i.e. something like /etc/athena/config), and each
containing a line of the form "key=value"? i think the only things i'd be
concerned about are that the transition from the current model to the new
one be as smooth as possible, and that we test it thoroughly.
from a support perspective it would also be nice but not essential to have
a utility analogous to irix's chkconfig which allows one to get a list of
all config variables in /etc/config as well as set and test them. with
all of them in separate files it becomes a lot easier to say "run these
three commands" as opposed to "edit this file to read x, then edit that
file to read y, etc."
cheers,
oliver
