From: Rob Landley <rob@landley.net>
To: linux-kernel@vger.kernel.org
Cc: David McCullough <david_mccullough@au.securecomputing.com>
Subject: Feature request: exec self for NOMMU.
Date: Tue, 26 Dec 2006 18:23:07 -0500 [thread overview]
Message-ID: <200612261823.07927.rob@landley.net> (raw)
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.
What would be really nice is if I could feed a NULL path to exec on NOMMU
systems, and have that mean "re-exec the current executable". I can't think
of a way to do this without kernel support. Any opinions on whether this is
worthwhile?
A nommu-friendly daemonize() is another use for this, by the way...
Rob
--
"Perfection is reached, not when there is no longer anything to add, but
when there is no longer anything to take away." - Antoine de Saint-Exupery
next reply other threads:[~2006-12-26 23:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-26 23:23 Rob Landley [this message]
2006-12-26 23:55 ` Feature request: exec self for NOMMU David Lang
2006-12-27 0:39 ` Rob Landley
2006-12-27 4:24 ` Denis Vlasenko
2006-12-27 5:44 ` Rob Landley
2006-12-27 5:13 ` Ray Lee
2006-12-27 5:51 ` Rob Landley
2006-12-27 6:08 ` Vadim Lobanov
2006-12-27 8:29 ` Rob Landley
2006-12-27 18:49 ` Ray Lee
2006-12-27 21:13 ` Rob Landley
2006-12-27 18:35 ` Denis Vlasenko
2006-12-27 21:03 ` Rob Landley
2006-12-28 2:48 ` Denis Vlasenko
2006-12-28 5:32 ` Rob Landley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200612261823.07927.rob@landley.net \
--to=rob@landley.net \
--cc=david_mccullough@au.securecomputing.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).