[Top][All Lists]

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

Re: [Fwd: Debugging execve problems]

From: Samuel Thibault
Subject: Re: [Fwd: Debugging execve problems]
Date: Sat, 7 Jan 2012 15:48:26 +0100
User-agent: Mutt/1.5.21+34 (58baf7c9f32f) (2010-12-30)

Svante Signell, le Sat 07 Jan 2012 15:43:46 +0100, a écrit :
> > test.sh:
> > #!/bin/sh
> > echo I'm $0
> > 
> > test.sh gets /dev/fd/3, which is not helpful for the IXLCL computation
> > above.
> Some questions related to the above:
> 1) I understand that if Emilos patches introducing a new RPC would be ABI and 
> API changes for
> all architectures there would be a problem, are they really? 

Not for all architectures, only for the hurd system. Interfaces are
usually a problem because they have to be kept around. If upstream
introduces a similar, but not exactly same interface, then it becomes
yet more difficult.

Antrik, do you know an easy way to introduce RPCs in an sort-of
"experimental" ID range, which would permit to introduce & test the RPCs
without conflicting with future upstream assignation?

> 2) How come execve calls a shell script works with . in PATH?

Sure they do, the problem is not there, but in the value of $0.

> 3) How come other architectures don't have this problem, and only Hurd
> has? 

Because Hurd is not Unix.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]