[44349] in Hotline Meeting

home help back first fref pref prev next nref lref last post

Re: cfd4 and scotland

daemon@ATHENA.MIT.EDU (Jonathon Weiss)
Thu Jul 30 15:43:35 1998

From: Jonathon Weiss <jweiss@MIT.EDU>
To: Matt Braun <matt@MIT.EDU>
Cc: John J Morey <jjmorey@MIT.EDU>, hotline@MIT.EDU, op@MIT.EDU
In-Reply-To: Your message of "Thu, 30 Jul 1998 13:50:54 EDT."
             <199807301750.NAA24959@forever.mit.edu> 
Date: Thu, 30 Jul 1998 15:43:31 EDT


> The typical procedure for a machine that was interupted in the middle of an
> update is to log in as root by some means (probably in this case a console
> login) and delete the last couple lines of /etc/athena/version.  This will
> make the workstation think it is still tunning the old release.  You can then
> re-run the update (following the instructions that jweiss mailed out in
> release-announce).

In general, this is the best bet, but there are a couple of caveats.
First, it is possible for some binaries to break and for this approach
not to succeed.  My guess is that this will usually be pretty
obivious, but I can't absolutely guarantee that.  Second, for the 8.1
to 8.2 update the Indy's temporarily boot onto a miniroot and then
perform the update itself.  Unfortunately, if the update is interupted
during this Matt's suggestion probably won't work.  rbasch might be
able to explain how to recover data from a system in this state.

	Jonathon


home help back first fref pref prev next nref lref last post