From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: qemu-devel-qX2TKyscuCcdnm+yROfE0A@public.gmane.org
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [Qemu-devel] Re: Making qemu images executable (and store command line arguments in them =P)
Date: Thu, 16 Aug 2007 08:23:16 +0300 [thread overview]
Message-ID: <46C3DF44.5040403@qumranet.com> (raw)
In-Reply-To: <46C3D109.3080807-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>
H. Peter Anvin wrote:
> Jorge Lucángeli Obes wrote:
>
>> The '#!' trick works nice with scripts, but I don't see it playing
>> very well with images. ¿Comments? ¿Pointers?
>>
>>
>
> Well, you can make it work with a header (you just have to pad it out to
> a fixed length or use a variable-offset format), but binfmt_misc might
> be a better choice.
>
>
binfmt_misc is Linux specific. And while kvm is a Linux thing now, qemu
isn't.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@qumranet.com>
To: qemu-devel@nongnu.org
Cc: kvm-devel@lists.sourceforge.net,
"Jorge Lucángeli Obes" <t4m5yn@gmail.com>
Subject: Re: [Qemu-devel] Re: [kvm-devel] Making qemu images executable (and store command line arguments in them =P)
Date: Thu, 16 Aug 2007 08:23:16 +0300 [thread overview]
Message-ID: <46C3DF44.5040403@qumranet.com> (raw)
In-Reply-To: <46C3D109.3080807@zytor.com>
H. Peter Anvin wrote:
> Jorge Lucángeli Obes wrote:
>
>> The '#!' trick works nice with scripts, but I don't see it playing
>> very well with images. ¿Comments? ¿Pointers?
>>
>>
>
> Well, you can make it work with a header (you just have to pad it out to
> a fixed length or use a variable-offset format), but binfmt_misc might
> be a better choice.
>
>
binfmt_misc is Linux specific. And while kvm is a Linux thing now, qemu
isn't.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
next prev parent reply other threads:[~2007-08-16 5:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-15 22:52 Making qemu images executable (and store command line arguments in them =P) Jorge Lucángeli Obes
2007-08-15 22:52 ` [Qemu-devel] " Jorge Lucángeli Obes
[not found] ` <59abf66e0708151552r6192f7e1he7ebe5bffd49525f-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-08-15 23:52 ` Mark Williamson
2007-08-15 23:52 ` Mark Williamson
2007-08-16 5:21 ` [kvm-devel] " Avi Kivity
2007-08-16 5:21 ` [kvm-devel] [Qemu-devel] " Avi Kivity
[not found] ` <200708160052.51858.mark.williamson-kDbDZe0LBGWFxr2TtlUqVg@public.gmane.org>
2007-08-16 16:11 ` Andreas Färber
2007-08-16 16:11 ` Andreas Färber
2007-08-16 4:22 ` H. Peter Anvin
2007-08-16 4:22 ` [Qemu-devel] Re: [kvm-devel] " H. Peter Anvin
[not found] ` <46C3D109.3080807-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>
2007-08-16 5:23 ` Avi Kivity [this message]
2007-08-16 5:23 ` Avi Kivity
2007-08-16 15:12 ` Luke -Jr
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=46C3DF44.5040403@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=qemu-devel-qX2TKyscuCcdnm+yROfE0A@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.