[2314] in Release_Engineering
Re: Major bugs in 7.0A: 7.0B available
daemon@ATHENA.MIT.EDU (Richard Basch)
Fri May 11 12:31:07 1990
Date: Fri, 11 May 90 12:28:56 -0400
To: dryfoo@MIT.EDU
Cc: Richard Basch <probe@MIT.EDU>, testers-announce@MIT.EDU
In-Reply-To: Gary L. Dryfoos's message of Fri, 11 May 90 12:00:14 EDT,
From: Richard Basch <probe@MIT.EDU>
If I did not make it clear in the original message, this is for machines
not in the "testers" cluster that have taken an update to 7.0.
Point 2... this is the second message to which people have replied to
testers-announce:
UNDER NO CIRCUMSTANCE SHOULD YOU REPLY TO THIS LIST UNLESS IT IS AN
URGENT MESSAGE THAT EVERYONE SHOULD SEE. (The only reason I am sending
this messagte to this list is to make this point clear).
-Richard
From: dryfoo@ATHENA.MIT.EDU
Date: Fri, 11 May 90 12:00:14 EDT
Here we go again...
} To: testers-announce@MIT.EDU
} Subject: Re: Major bugs in 7.0A: 7.0B available
} From: Richard Basch <probe@MIT.EDU>
...
} Updating to 7.0 and having it reboot will cause the machine to then try
} updating back to 6.4... this WILL fail, and it generates a mess that is
} non-trivial to clean up. (This was a bug on the 6.4 packs which has
} been fixed in 7.0).
}
} -Richard
This APPEARS to mean and imply:
"After you have taken the 7.0 updates, you should not allow your
workstation to reboot under any circumstances. In particular, you can
now no longer get a workstation out of a hung state with the useful,
all-purpose, reboot button. From now on (until some other, unspecified
release) you're just stuck."
If this is not what you meant to say or imply, please clarify.
Thank you,
-- Gary Dryfoos
Chairman, SCM
