Re: Feature request: exec self for NOMMU.

From: Denis Vlasenko
Date: Wed Dec 27 2006 - 13:38:45 EST

On Wednesday 27 December 2006 06:13, Ray Lee wrote:
> On 12/26/06, Rob Landley <rob@xxxxxxxxxxx> wrote:
> > I'm trying to make some nommu-friendly busybox-like tools, which means using
> > vfork() instead of fork(). This means that after I fork I have to exec in
> > the child to unblock the parent, and if I want to exec my current executable
> > I have to find out where it lives so I can feed the path to exec(). This is
> > nontrivial.
> >
> > Worse, it's not always possible. If chroot() has happened since the program
> > started, there may not _be_ a path to my current executable available from
> > this process's current or root directories.
> How about openning an fd to yourself at the beginning of execution, then calling
> fexecve later?

This solves chroot problem. How to find path-to-yourself reliably
(for one, without using /proc/self/exe) is not obvious to me.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at