[258] in SIPB-AFS-requests
Re: Ronald-Ann
daemon@ATHENA.MIT.EDU (dkk@ATHENA.MIT.EDU)
Fri Jul 27 12:30:53 1990
From: dkk@ATHENA.MIT.EDU
Date: Fri, 27 Jul 90 12:30:05 -0400
To: qjb@ATHENA.MIT.EDU
Cc: sipb-afsreq@ATHENA.MIT.EDU
In-Reply-To: Emanuel 'Jay' Berkenbilt's message of Fri, 27 Jul 90 10:11:32 -0400, <9007271411.AA11407@soup.MIT.EDU>
> I updated it to 3.0 proper the same day the athena cell was updated.
Then please clarify this for me:
From what I understand, 3.0b2 "butc" interprets the contents of
/usr/afs/backup/tapeconfig as the number of bytes of data that the
tape can hold, while the 3.0release version interprets it as the
number of *K*bytes it can hold. The /afs/sipb/service/@sys/butc,
which is the version that works with the SIPB cell, seems to expect
the (I believe) old format. The butc that Ezra used for another cell
(on the same vs2 I'm using - Alecto) has an RCS header from a check-in
by Liz Hines on 90/03/90. The butc in the SIPB cell doesn't have any
RCS headers from this year.
What confuses me now is that I remember the relatively up-to-date butc
on Alecto not working in the SIPB cell (though I don't remember the
error(s)). I'm told there are many different versions of butc and
backup, and that a 3.0b2 version almost certainly doesn't work with a
3.0r version.
Perhaps I just misdiagnosed the failure I had with the other butc.
I'll try that one again (as safely as possible) to try to figure out
what's up.
Jay: I put your root instance in alecto:/.klogin again.
