On 19 May 2002, Thomas Bushnell, BSG wrote:
> Passive translators are, by convention, stored in /hurd. It's not
> settrans that lacks a search path capability, but rather the parent
> filesystem that lacks it. And part of that is because the user's
> context is long gone by the time the translator is started. The
> settrans program just squirrels its arguments away into the
> filesystem, and then when the requested node is opened, the specified
> command is run as a translator.
Why can't settrans fetch $ENV{'PATH'}, and squirrel that away?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
