From: Rob Landley <rob@landley.net>
To: Denis Vlasenko <vda.linux@googlemail.com>
Cc: David Lang <david.lang@digitalinsight.com>,
linux-kernel@vger.kernel.org,
David McCullough <david_mccullough@au.securecomputing.com>
Subject: Re: Feature request: exec self for NOMMU.
Date: Wed, 27 Dec 2006 00:44:11 -0500 [thread overview]
Message-ID: <200612270044.12645.rob@landley.net> (raw)
In-Reply-To: <200612270524.36157.vda.linux@googlemail.com>
On Tuesday 26 December 2006 11:24 pm, Denis Vlasenko wrote:
> busybox needs it in order to spawn, for example, gzip/bzip2 helper
> for tar. We know that our own executable has this function.
> How to execute _our own executable_? exec("/proc/self/exe")
> works only if /proc is mounted. I can imagine that some embedded
> people want to be able to not rely on that.
Actually, we added CONFIG_BUSYBOX_EXEC_PATH so you could feed it a different
path to the busybox executable if you haven't got proc. It's still a hack,
and it still breaks when you chroot, but you can use the standalone shell
without /proc.
Why do people chroot? To do system recovery using busybox with the standalone
shell and built-in commands. They chroot into the damaged root partition to
run some of the commands in there (shared library paths get a bit twitchy
without the chroot), but they want to use the built-in busybox commands for
most of it because PAM and selinux can get screwed up by passing birds,
brightly colored wallpaper or large flowers, and when they do they interfere
with everything.
*shrug* This was a bigger deal a few years ago, before the invention of the
knoppix CD...
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 prev parent reply other threads:[~2006-12-27 5:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-26 23:23 Feature request: exec self for NOMMU Rob Landley
2006-12-26 23:55 ` David Lang
2006-12-27 0:39 ` Rob Landley
2006-12-27 4:24 ` Denis Vlasenko
2006-12-27 5:44 ` Rob Landley [this message]
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=200612270044.12645.rob@landley.net \
--to=rob@landley.net \
--cc=david.lang@digitalinsight.com \
--cc=david_mccullough@au.securecomputing.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vda.linux@googlemail.com \
/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).