[17697] in Athena Bugs
Re: references to /mit/infoagents in lynx shell scripts
daemon@ATHENA.MIT.EDU (Jonathon Weiss)
Thu Mar 23 21:29:54 2000
Date: Thu, 23 Mar 2000 21:29:48 -0500 (EST)
Message-Id: <200003240229.VAA23315@speaker-for-the-dead.mit.edu>
To: Matthew Munsey <mmunsey@mit.edu>
CC: Greg Hudson <ghudson@mit.edu>, bug-infoagents@mit.edu
In-reply-to: "[17382] in Athena Bugs"
From: Jonathon Weiss <jweiss@MIT.EDU>
Hi,
Some time ago, you reported a bug, and Greg Hudson replied:
> 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.
I've discussed this issue with Todd, and while it is possible that he
may get to this eventually, it is an extremely low priority and as
such, not likely to happen any time soon. Rather than let your bug
report languish, I wanted to let you know what the status was and
close the bug report in our system. If this is really problematic for
you I can re-open the report, but it is unlikely to affect the
outcome.
Jonathon Weiss
jweiss@mit.edu
MIT IS/Athena Programmer
