[305] in Release_7.7_team
sgi upgrading alternatives
daemon@ATHENA.MIT.EDU (Mike Barker)
Wed May 10 12:17:21 1995
From: Mike Barker <mbarker@MIT.EDU>
To: acmg@MIT.EDU, dcns-dev@MIT.EDU, release-team@MIT.EDU, skunks@MIT.EDU,
ops@MIT.EDU, tjm@MIT.EDU, gjackson@MIT.EDU, nschmidt@MIT.EDU,
carla@MIT.EDU, bmurphy@MIT.EDU, bwmelans@MIT.EDU, kim@MIT.EDU,
vrt@MIT.EDU, cfields@MIT.EDU, dot@MIT.EDU, alexp@MIT.EDU
Date: Wed, 10 May 1995 12:16:38 EDT
As far as I can tell, these are the alternatives that are available.
Option 1 is not feasible, but I include it for completeness.
Option 1. Don't upgrade XL machines; postpone installing XZ machines
Use IRIX 5.2/AFS 3.3a (do nothing-- UPSET EVERYONE)
Option 2. Don't upgrade XL machines; install new XZ machines
Use IRIX 5.2/AFS 3.3a (no demos on XZ; 3PSW may not work)
Option 3. Upgrade XL machines; install new XZ machines
Use IRIX 5.2/AFS 3.3a (no demos on XZ; 3PSW may not work)
Option 4. Don't upgrade XL machines; install new XZ machines
Mix--IRIX 5.2/AFS 3.3a on XL; IRIX 5.3/AFS 3.4 on XZ
(support nightmare)
Option 5. Upgrade XL machines; install new XZ machines
Use IRIX 5.3/AFS 3.4
All options will require some work on the install server.
Since there doesn't seem to be much gain in holding back on upgrading
XL machines, only options 3 and 5 are realistic. Option 5 is optimal,
but depends on availability of AFS 3.4.
I think Option 3 is the most likely alternative. It will require
testing to check that the key applications operate.
If anyone has any other alternatives, please let me know.
thanks.
mike
