Re: hurd does NOT need /hurd
tb@becket.net (Thomas Bushnell, BSG) writes:
> Richard Kettlewell <richardk@chiark.greenend.org.uk> writes:
>> I don't follow you at all. Why is the user giving the exact command
>> line rather than something that can be searched for in a path, as with
>> conventional program execution? I'd like to know what the relevant
>> difference is.
>>
>> (I think that #! should honor PATH, but it seems unlikely that I'd win
>> that battle.)
>
> Because the user's PATH is long gone when the translator is invoked.
> The normal case of settrans squirrels the command away, and later
> when someone starts accessing that filesystem, it gets executed--in
> the context of whatever parent filesystem it's "mounted" on.
> (Actually, that context is carefully managed so that it's as vanilla
> and default as possible.)
I still don't see why settrans can't search some kind of path list (or
add a fixed prefix to relative names for that matter, it'd be "/hurd/"
on current systems presumably) before the 'squirrelling' step.
Sorry if this seems obtuse; it's possible I've missed some vital fact
that seems to you to be too obvious to be worth mentioning.
--
http://www.greenend.org.uk/rjk/
--
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: