[3184] in SIPB-AFS-requests
Re: Thoughts on upgrading the SIPB cell
daemon@ATHENA.MIT.EDU (Greg Hudson)
Tue Nov 24 15:02:00 1998
To: Garry Zacheiss <zacheiss@MIT.EDU>
Cc: sipb-afsreq@MIT.EDU
In-Reply-To: Your message of "Tue, 24 Nov 1998 03:10:43 EST."
<199811240810.DAA00166@sweet-transvestite.mit.edu>
Date: Tue, 24 Nov 1998 15:01:13 EST
From: Greg Hudson <ghudson@MIT.EDU>
> but updating the cell to 3.4a could still possibly happen before
> then, since there should be little to no data inaccessibility for
> that upgrade, beyond what is normally noticed with the weekly
> restart.
Post-drop-date paranoia applies to possibly destabilizing changes as
well as changes we know will cause outages. So we should wait until
after finals.
Obviously, running 3.4a on Ultrix carries a certain risk because
nobody else does it, but I think the simplification it provides us is
worth the risk. So I think doing this upgrade shortly after finals is
a fine idea.
I believe that jhawk et al would like us to start maintaining a SIPB
copy of the AFS sources consequent with the AFS upgrade, and do our
own builds. (Right now /afs/sipb/service/afs contains a symlink farm
to the afsdev locker, which doesn't really count.) This should be
pretty straightforward.
