[17382] in Athena Bugs
Re: references to /mit/infoagents in lynx shell scripts
daemon@ATHENA.MIT.EDU (Greg Hudson)
Sun Nov 21 22:40:54 1999
Message-Id: <199911220340.WAA04503@small-gods.mit.edu>
To: Matthew Munsey <mmunsey@MIT.EDU>
cc: bug-infoagents@MIT.EDU
In-Reply-To: Your message of "Sun, 21 Nov 1999 22:00:04 EST."
<3.0.5.32.19991121220004.00b35300@po8.mit.edu>
Date: Sun, 21 Nov 1999 22:40:44 -0500
From: Greg Hudson <ghudson@MIT.EDU>
Bruce Lewis no longer works for MIT, incidentally. I'm answering as
the Athena release engineer; Todd Belton will make the actual decision
as to what to do with the infoagents locker.
> When executing binaries in many Athena lockers, I find it preferable
> to simply type ~lockername/bin/binaryname rather than going to the
> trouble of adding or attaching lockers.
This method of invoking programs from lockers is not supported.
Locker software is not guaranteed to work when the locker is not
attached.
> the conflict of binaries in the Athena locker path with commonly
> used local programs.
Locker software should still work when lockers are attached but not in
the path. So if this is the problem, you can simply attach the locker
and then run the program from `athdir /mit/lockername` (technically
correct) or ~lockername/bin (will work most of the time).
> The obvious solution in my mind is the use of the full path in the
> shell script reference to the lynx binary
That would be poor; it would negate the desirable property that a
locker can be copied somewhere other than its AFS path and still work.
> or alternatively a minimal attach of the infoagents locker (as is
> done with sipb, graphics, and gnu
This would be reasonable if Todd wants to do it.
