From: Luke -Jr <luke@dashjr.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [kvm-devel] Making qemu images executable (and store command line arguments in them =P)
Date: Thu, 16 Aug 2007 15:12:43 +0000 [thread overview]
Message-ID: <200708161512.43378.luke@dashjr.org> (raw)
In-Reply-To: <46C3D109.3080807@zytor.com>
On Thursday 16 August 2007, 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.
Can't hurt to support both, can it? ;)
prev parent reply other threads:[~2007-08-16 15:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-15 22:52 [Qemu-devel] Making qemu images executable (and store command line arguments in them =P) Jorge Lucángeli Obes
2007-08-15 23:52 ` Mark Williamson
2007-08-16 5:21 ` [kvm-devel] " Avi Kivity
2007-08-16 16:11 ` Andreas Färber
2007-08-16 4:22 ` [Qemu-devel] Re: [kvm-devel] " H. Peter Anvin
2007-08-16 5:23 ` Avi Kivity
2007-08-16 15:12 ` Luke -Jr [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=200708161512.43378.luke@dashjr.org \
--to=luke@dashjr.org \
--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).