From: Avi Kivity <avi@qumranet.com>
To: Markus Hitter <mah@jump-ing.de>
Cc: kvm-devel@lists.sourceforge.net, qemu-devel@nongnu.org
Subject: Re: [kvm-devel] [Qemu-devel] Making qemu images executable (and store command line arguments in them =P)
Date: Sun, 19 Aug 2007 14:08:34 +0300 [thread overview]
Message-ID: <46C824B2.1040300@qumranet.com> (raw)
In-Reply-To: <99222E0B-B4B8-4D5A-A557-1A9CF113E9E7@jump-ing.de>
Markus Hitter wrote:
> Am 19.08.2007 um 12:35 schrieb Avi Kivity:
>
>
>> - this deviates from standard Unix (and Windows) practice.
>> Arguably the OS X way is superior, but qemu is perhaps not the best
>> vehicle to introduce it to other OSes.
>>
>
> NeXTstep introduced this into the Unix world and GNUstep uses it
> today. So, there's prior art.
>
>
Nothing on my machine uses it today, as far as I can tell.
(I don't oppose this use in Linux -- I think it's an excellent way to
package apps -- but I'm not sure qemu should be the first app to do
this. It needs buy-in from distros)
((but we're actually talking about something slightly different;
packaging data vs packaging apps))
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2007-08-19 11:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-16 17:05 [Qemu-devel] Making qemu images executable (and store command line arguments in them =P) Ben Taylor
2007-08-16 20:36 ` Dan Shearer
2007-08-17 12:40 ` [kvm-devel] " Avi Kivity
2007-08-17 13:09 ` Christian Brunschen
2007-08-19 10:35 ` Avi Kivity
2007-08-19 11:04 ` Markus Hitter
2007-08-19 11:08 ` Avi Kivity [this message]
2007-08-19 13:14 ` Christian Brunschen
-- strict thread matches above, loose matches on Subject: below --
2007-08-15 22:52 Jorge Lucángeli Obes
2007-08-15 23:52 ` Mark Williamson
2007-08-16 5:21 ` [kvm-devel] " Avi Kivity
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=46C824B2.1040300@qumranet.com \
--to=avi@qumranet.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=mah@jump-ing.de \
--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).