[675] in testers
Re: 7.0b update script
daemon@ATHENA.MIT.EDU (daemon@ATHENA.MIT.EDU)
Fri May 11 13:06:11 1990
Date: Fri, 11 May 90 13:05:38 -0400
To: Ken Raeburn <Raeburn@MIT.EDU>
Cc: testers@MIT.EDU
In-Reply-To: Ken Raeburn's message of Fri, 11 May 90 12:53:34 -0400,
From: Richard Basch <probe@MIT.EDU>
1. Run "mkserv afs"... it doesn't do everything, but it does configure
your machine to support AFS service. Currently, it has no notion
of the binaries needed for updating and it mentions that.
2. You are correct in the fact that /etc/fsck did not get replaced.
7.0B was configured as an incremental release (as will 7.0C be),
and the incremental updates do not invoke "track". On PUBLIC
machines, it never considers an update to just be an incremental;
a full check is done on those machines.
Poll: should #2 persist in the way it is, or should it insist on running
track? Each configuration file for each release number indicates
whether a full update should be done, or if it was simply a few
configuration files that have changed. Any change in the numbers (ie.
from 7.0 to 7.1) are automatically considered full-updates, already.
-Richard
