[2076] in Release_7.7_team
Re: Linux update
daemon@ATHENA.MIT.EDU (Greg Hudson)
Thu Feb 3 10:23:17 2000
Message-Id: <200002031523.KAA12061@small-gods.mit.edu>
To: tb@MIT.EDU (Thomas Bushnell, BSG)
Cc: Greg Hudson <ghudson@MIT.EDU>, release-team@MIT.EDU
In-Reply-To: Your message of "03 Feb 2000 10:16:57 EST."
<u1hsnzaiady.fsf@opus.mit.edu>
Date: Thu, 03 Feb 2000 10:23:09 -0500
From: Greg Hudson <ghudson@MIT.EDU>
> I have no objection to Greg's proposed alteration of the update
> scheme, except that I do strongly object to any patch scripts that
> don't live in one package or another. It should be fine to put the
> script into the athena-ws package, say.
Could you elaborate on how you see this working?
Things update scripts have done include converting old attachtabs to
new ones, modifying variable definitions in rc.conf (like MACHINE),
inaugurating files like /etc/athena/access, etc. We typically want to
run them once, when the machine takes the update, and not after that.
