From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Gc6vv-0000Cj-9T for qemu-devel@nongnu.org; Mon, 23 Oct 2006 17:02:07 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Gc6vs-0000Ad-36 for qemu-devel@nongnu.org; Mon, 23 Oct 2006 17:02:05 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Gc6vr-0000AN-Ia for qemu-devel@nongnu.org; Mon, 23 Oct 2006 17:02:03 -0400 Received: from [12.7.175.14] (helo=mx2.palmsource.com) by monty-python.gnu.org with esmtp (Exim 4.52) id 1Gc6vq-00067h-Hm for qemu-devel@nongnu.org; Mon, 23 Oct 2006 17:02:02 -0400 Message-ID: <453D2DBF.1060803@palmsource.com> Date: Mon, 23 Oct 2006 14:01:51 -0700 From: "K. Richard Pixley" MIME-Version: 1.0 Subject: Re: [Qemu-devel] config file support References: <200610221751.50317.rob@landley.net> <453D00CD.6010307@palmsource.com> <200610231639.00717.rob@landley.net> In-Reply-To: <200610231639.00717.rob@landley.net> Content-Type: multipart/alternative; boundary="------------050109010105050505000805" Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Rob Landley Cc: qemu-devel@nongnu.org This is a multi-part message in MIME format. --------------050109010105050505000805 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Rob Landley wrote: >> What's the difference between a shell script to cover qemu and a >> #!/bin/qemu config file? >> > The shell script works now, and you're proposing breaking it? > No, I'm not. I'm genuinely asking about functional differences. >> Am I missing any significant functionality differences? >> > So you'd have no trouble configuring kde's file type associations to open > arbitrary "*.img" files with qemu when you click on them if you couldn't do > this entirely from the command line? > I don't use kde. And *.img is used for far too many file types to assume that this alone indicates that any foo.img is a qemu related file. But yes, I could configure gnome to do this. Or firefox. It's pretty much trivial. MacosX has file system metadata to help out so that it doesn't have to rely solely on the irrelevant file name suffixes. --rich --------------050109010105050505000805 Content-Type: text/html; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Rob Landley wrote:
What's the difference between a shell script to cover =
qemu and a=20
#!/bin/qemu config file?
    
The shell script works now, and you're proposing =
breaking it?
No, I'm not.=A0 I'm genuinely asking about functional differences.
Am I missing any significant functionality differences=
?
    
So you'd have no trouble configuring kde's file t=
ype associations to open=20
arbitrary "*.img" files with qemu when you click on them if you couldn't =
do=20
this entirely from the command line?
I don't use kde.=A0 And *.img is used for far too many file types to assume that this alone indicates that any foo.img is a qemu related file.

But yes, I could configure gnome to do this.=A0 Or firefox.=A0 It's prett= y much trivial.=A0 MacosX has file system metadata to help out so that it doesn't have to rely solely on the irrelevant file name suffixes.

--rich
--------------050109010105050505000805--