From: "Anderson Lizardo" <anderson.lizardo@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] -chroot and -su options.
Date: Fri, 14 Mar 2008 12:06:29 -0400 [thread overview]
Message-ID: <5b5833aa0803140906n210c245fof5889f7c7c4e8a68@mail.gmail.com> (raw)
In-Reply-To: <200803031828.22657.rob@landley.net>
Hi,
On Mon, Mar 3, 2008 at 8:28 PM, Rob Landley <rob@landley.net> wrote:
> Quick and dirty patch to teach qemu application emulation how to chroot (and
> drop privs), so you don't have to pollute a target filesystem with host code,
> and/or figure out how to build qemu static in order to run a dynamic binary.
I tested your patch, but it doesn't seem to work when the application
forks a new process (the new process is attempted to run as a native
host executable, instead of with qemu). Is that expected?
I tried enabling binfmt for it, but then qemu needs to be static,
defeating the purpose of this option.
Regards,
--
Anderson Lizardo
Instituto Nokia de Tecnologia
Manaus - Brazil
prev parent reply other threads:[~2008-03-14 16:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-04 0:28 [Qemu-devel] [PATCH] -chroot and -su options Rob Landley
2008-03-04 11:22 ` Edgar E. Iglesias
2008-03-05 6:51 ` Rob Landley
2008-03-05 7:54 ` Edgar E. Iglesias
2008-03-06 6:47 ` Rob Landley
2008-03-14 14:08 ` Edgar E. Iglesias
2008-03-14 15:26 ` Rob Landley
2008-03-14 16:06 ` Anderson Lizardo [this message]
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=5b5833aa0803140906n210c245fof5889f7c7c4e8a68@mail.gmail.com \
--to=anderson.lizardo@gmail.com \
--cc=qemu-devel@nongnu.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).