[5170] in Release_7.7_team
Re: acrobat default update
daemon@ATHENA.MIT.EDU (Alex T Prengel)
Sun Jun 19 03:02:29 2005
Message-Id: <200506190702.j5J72EJ3020190@astrophel.mit.edu>
To: Greg Hudson <ghudson@MIT.EDU>
cc: alexp@MIT.EDU, ops@MIT.EDU, release-team@MIT.EDU
In-Reply-To: Your message of "Sat, 18 Jun 2005 16:07:38 EDT."
<1119125258.3705.77.camel@egyptian-gods.mit.edu>
Date: Sun, 19 Jun 2005 03:02:14 -0400
From: Alex T Prengel <alexp@MIT.EDU>
X-Spam-Score: 0.932
X-Spam-Flag: NO
>>Since I presume my suggestion would not affect local-lockers
>>operation, I'd like to implement it> Since I presume my suggestion
>>would not affect local-lockers operation, I'd like to implement it
>Your suggestion would affect local-lockers operation in that the
>local-lockers script will try to read the /mit/acro/current symlink
>value, will get ".current/@sys", and will fail.
>
>Unfortunately, I'm on vacation for two weeks, so I won't be putting out
>patch releases to update local-lockers.conf until July. I'd suggest
>leaving ~acro/current with the value of acro_v5.0.10 for now
OK- then I'll leave the "current" link as is for now, and Monday night change
the Linux version in the base locker script to 7.0. I presume the effect
of this will be:
Suns still run 5.0.10 locally.
Linux machines run 7.0 out of AFS.
which will be OK until local-lockers is updated; I think, if I understand
local-lockers.conf correctly, that when you update it to use acro/current.@sys,
that it then will be OK to use my double symlink idea so users can follow
"current" to the right locker in both cases...
Alex
