[17381] in Athena Bugs

home help back first fref pref prev next nref lref last post

references to /mit/infoagents in lynx shell scripts

daemon@ATHENA.MIT.EDU (Matthew Munsey)
Sun Nov 21 22:00:13 1999

Message-Id: <3.0.5.32.19991121220004.00b35300@po8.mit.edu>
Date: Sun, 21 Nov 1999 22:00:04 -0500
To: special address <bug-infoagents@MIT.EDU>
From: Matthew Munsey <mmunsey@MIT.EDU>
Cc: Bruce Lewis <brlewis@MIT.EDU>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

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.  I realize there are some advantages to
adding/attaching a locker (filesystem zephyr notification, augmentation of
path), but frequently I don't need the overhead of this function or the
conflict of binaries in the Athena locker path with commonly used local
programs.

Unfortunately, I recently realized that the execution of lynx requires the
attachment of infoagents, because the scripts that call it refer to
/mit/infoagents for various filenames.  While there is an advantage to afs
path abstraction, this simplification is the only problem to cause
invocation via ~infoagents/bin/lynx to fail.  The obvious solution in my
mind is the use of the full path in the shell script reference to the lynx
binary, or alternatively a minimal attach of the infoagents locker (as is
done with sipb, graphics, and gnu).  I imagine modifications along the same
lines might simplify the scripts calling netscape and other programs, but I
realize that some programs will not function happily without being in the
path.  Here is the full path to the shell script in question:

/afs/athena.mit.edu/software/infoagents/arch/share/bin/lynx-2.7.1MIT

Thanks,
Matt

home help back first fref pref prev next nref lref last post