[2035] in Release_7.7_team
Re: contents of athena-base package
daemon@ATHENA.MIT.EDU (Greg Hudson)
Tue Jan 11 12:45:15 2000
Message-Id: <200001111744.MAA07729@small-gods.mit.edu>
To: tb@MIT.EDU (Thomas Bushnell, BSG)
Cc: release-team@MIT.EDU, source-developers@MIT.EDU
In-Reply-To: Your message of "11 Jan 2000 12:37:52 EST."
<u1hwvpg1pcf.fsf@steve-dallas.mit.edu>
Date: Tue, 11 Jan 2000 12:44:40 -0500
From: Greg Hudson <ghudson@MIT.EDU>
> As per discussion on linux-testers, most of these variables can be
> moved into per-package scripts; this is less confusing and makes
> things niftier.
mkserv will eventually need modification if we do this. I still think
we probably should, though.
> /etc/athena/rc.conf would then contain only those variables that
> cluster modifies, and the whole file can then be moved into
> athena-ws.
I would refine this slightly: /etc/athena/rc.conf would contain only
those variables which modify machine configuration not corresponding
to any Athena package. Traditionally, this has included things like
turning on or off the NFS server.
> /usr/athena/man/mandesc
Since every Athena package should include man pages, I guess this is
the one thing which does belong in an athena-base package.
> /etc/athena/version
> athena-base currently inaugurates this file. If we punt
> athena-base, then something should do it. If we move it into
> athena-ws, then we need to deal with all the other programs that
> depend on /etc/athena/version being sensible. Perhaps that's not
> too hard, but I'd appreciate others' thoughts.
I don't mind having this in athena-base given that we also need
mandesc.
