From: Johannes Schauer <j.schauer@email.de>
To: Riku Voipio <riku.voipio@iki.fi>
Cc: stappers@stappers.nl, 632192@bugs.debian.org,
qemu-devel@nongnu.org, josch <josch@pyneo.org>
Subject: Re: [Qemu-devel] [PATCH] add QEMU_LD_PREFIX environment variable
Date: Thu, 28 Jul 2011 13:24:47 +0200 [thread overview]
Message-ID: <20110728112447.GA20506@hoothoot> (raw)
In-Reply-To: <20110728084109.GA20285@afflict.kos.to>
Hi,
On Thu, Jul 28, 2011 at 11:41:09AM +0300, Riku Voipio wrote:
> On Sat, Jul 23, 2011 at 07:47:49AM +0200, josch wrote:
> > This could be avoided by setting the proposed environment variable
> > QEMU_LD_PREFIX to the just
> > created debian rootfs. As mentioned earlier, the usage of the -L option
> > is not possible in this scenario because qemu-user is only implicitly
> > called by the binfmt mechanism.
>
> What worries me here is that we are beginning to add a enviroment
> variable for each and every command line option of qemu linux-user.
Are there other environment variables? I didnt see any? (well besides
QEMU_STRACE that is)
> I think it would be better to have a wrapper binary to be registered
> as the binfmt runner.
If you need help with writing something - dont hesitate to ask for help.
I'm very interested in having this functionality working because of the
reasons I gave in my initial mail. [1]
> Alternatively we should have a generic setup for mapping enviroment
> variables to command line options. Now we get special per-option code
> every time someone needs to setup a command line option from binfmt.
What other options are there that would be interesting for binfmt?
I was also sending this patch to qemu-devel list a month ago but got no
reply. [2]
As I said - if you would like a wrapper or a generic setup for mapping
env variables to commandline parameters and dont have time to do it
yourself, dont hesitate to delegate some work to me :)
@Geert Stappers:
you are patching bsd-user/main.c and darwin-user/main.c as well. I take
it that you did test your changes on those platforms? does it work there
as well? I have no clue of darwin but is it really useful there?
cheers, josch
[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=632192#5
[2] http://lists.nongnu.org/archive/html/qemu-devel/2011-07/msg00459.html
next prev parent reply other threads:[~2011-07-28 11:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-23 5:47 [Qemu-devel] [PATCH] add QEMU_LD_PREFIX environment variable josch
2011-07-23 5:47 ` josch
2011-07-28 8:41 ` Riku Voipio
2011-07-28 11:24 ` Johannes Schauer [this message]
2011-07-28 16:50 ` Geert Stappers
2011-07-28 17:28 ` Alexander Graf
2011-07-29 12:52 ` [Qemu-devel] Bug#632192: " Vagrant Cascadian
2011-07-29 15:21 ` Johannes Schauer
2011-07-30 13:58 ` Riku Voipio
2011-07-31 11:51 ` [Qemu-devel] [PATCH] introduce environment variables for all qemu-user options j.schauer
2011-07-31 12:12 ` Peter Maydell
2011-07-31 21:40 ` Johannes Schauer
2011-08-05 10:04 ` Peter Maydell
2011-08-06 6:54 ` Johannes Schauer
2011-08-20 17:29 ` Yann Dirson
-- strict thread matches above, loose matches on Subject: below --
2011-07-06 9:15 [Qemu-devel] [PATCH] add QEMU_LD_PREFIX environment variable Johannes Schauer
2011-07-06 9:15 ` Johannes Schauer
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=20110728112447.GA20506@hoothoot \
--to=j.schauer@email.de \
--cc=632192@bugs.debian.org \
--cc=josch@pyneo.org \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@iki.fi \
--cc=stappers@stappers.nl \
/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).