Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

ading Postscript files




Dale R Worley wrote in a message to Mike Bilow:

 DRW> One would think that one could invent a new special
 DRW> directory name to mean "the directory in which the current
 DRW> executable resides" (Multics has this concept), but it can't
 DRW> be done, because that directory has no unambiguous
 DRW> definition -- the executable file can be hardlinked from
 DRW> several different directories, and all of the links to the
 DRW> file are equal.

One ordinarily runs tools and utilities out of the search path, but not full
blown applications.  If this is really an issue, then the parent executable can
be replaced by a shell script that first sets the current directory and then
invokes the original parent executable.  Eventually you hit a limit of
practicality: the user has to be expected to know what is on the machine and
what will be running from where.  Unix is open to a lot of fair criticism, but
not on the ground that it can't read minds.
 
-- Mike





BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org