[60409] in Hotline Meeting

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

Re: m-tor.mit.edu not able to take update

daemon@ATHENA.MIT.EDU (Marshall Vale)
Mon Jul 22 11:07:57 2002

Mime-Version: 1.0
Message-Id: <a05200301b961cf215488@[18.18.1.144]>
In-Reply-To: 
 <Pine.GSO.4.30L.0207191336350.19154-100000@pullman-standard.mit.edu>
Date: Mon, 22 Jul 2002 11:07:54 -0400
To: <hotline@MIT.EDU>
From: Marshall Vale <mjv@MIT.EDU>
Cc: "Paul B. Hill" <pbh@MIT.EDU>, <ops@MIT.EDU>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"

At 1:38 PM -0400 7/19/02, Cana Lynn McCoy wrote:
>On Fri, 19 Jul 2002, Paul B. Hill wrote:
>
>>  The hesiod information for MUEHLBURGER-TOR is not correct.
>>
>>  We tried to update the machine to the new Athena release and it is now
>>  unusable. The machine is a Sunblade 100 in W92-172.
>
>It looks like the hesiod information was never updated after the machine
>was upgraded to a Sunblade.
>
>I'll give it correct information, which will propagate with the next dcm.

So I've let the dcm take effect, reboot the box since it was in a 
useless state, and have now tried to update to 9.1 again. Following 
the instructions that Greg sends out in his e-mail yields the helpful 
message of "It appears you already have this update."

How do I force it to reupdate to 9.1 again? Or better yet, with it in 
such a busted state, how do it just get it working again? I needed 
this machine working last Friday and I desperately need it working 
today and from where I stand, there isn't anything obvious for me to 
do here other than wish the stupid thing were in pieces.

Marshall

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