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,
=?ISO-8859-1?Q?Jorge_Luc=E1ngeli_?=@sc8-sf-spam2.sourceforge.net
Subject: Re: Re : [Qemu-devel] Re: Making qemu images executable (and store command line arguments in them =P)
Date: Thu, 16 Aug 2007 11:16:37 +0300 [thread overview]
Message-ID: <46C407E5.5050607@qumranet.com> (raw)
In-Reply-To: <497154.10348.qm-kfZ4Lx4gWRrGRxTy+Q50vsz6deESKz/lQQ4Iyu8u01E@public.gmane.org>
Sylvain Petreolle wrote:
>> ----- Message d'origine ----
>> De : Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
>> À : qemu-devel-qX2TKyscuCcdnm+yROfE0A@public.gmane.org
>> Cc : kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org; Jorge Lucángeli Obes <t4m5yn@gmail.com>
>> Envoyé le : Jeudi, 16 Août 2007, 7h23mn 16s
>> Objet : Re: [Qemu-devel] Re: [kvm-devel] Making qemu images executable (and store command line arguments in them =P)
>>
>>
>>> 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.
>>
>>
> Wouldnt be #! Linux specific too ?
>
It's unix-specific, not Linux-specific. Windows users can change file
associations to have qemu run .qcow files.
--
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/
prev parent reply other threads:[~2007-08-16 8:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-16 7:35 Re : [Qemu-devel] Re: Making qemu images executable (and store command line arguments in them =P) Sylvain Petreolle
[not found] ` <497154.10348.qm-kfZ4Lx4gWRrGRxTy+Q50vsz6deESKz/lQQ4Iyu8u01E@public.gmane.org>
2007-08-16 8:16 ` Avi Kivity [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=46C407E5.5050607@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc==?ISO-8859-1?Q?Jorge_Luc=E1ngeli_?=@sc8-sf-spam2.sourceforge.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox