From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1KNZS8-0000QY-BI
	for qemu-devel@nongnu.org; Mon, 28 Jul 2008 16:36:20 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1KNZS7-0000Q6-54
	for qemu-devel@nongnu.org; Mon, 28 Jul 2008 16:36:20 -0400
Received: from [199.232.76.173] (port=58601 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1KNZS7-0000Q0-0K
	for qemu-devel@nongnu.org; Mon, 28 Jul 2008 16:36:19 -0400
Received: from mail.codesourcery.com ([65.74.133.4]:40260)
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60)
	(envelope-from <paul@codesourcery.com>) id 1KNZS6-0007x3-ME
	for qemu-devel@nongnu.org; Mon, 28 Jul 2008 16:36:18 -0400
From: Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] [PATCH] qcow3 - arbitrary metadata
Date: Mon, 28 Jul 2008 21:36:02 +0100
References: <a38baa500807281256s7aa6c69em344c655145956b24@mail.gmail.com>
	<488E2752.7030008@codemonkey.ws>
	<a38baa500807281324h7b1a0cc4ide06a589277052f8@mail.gmail.com>
In-Reply-To: <a38baa500807281324h7b1a0cc4ide06a589277052f8@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200807282136.03400.paul@codesourcery.com>
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org
Cc: Nathaniel McCallum <nathaniel@natemccallum.com>

> Ease of use primarily. =A0Take the case of a VM appliance. =A0I would bui=
ld a
> VM appliance and in the metadata I would put:
> 1. My company's logo (which would show up as the icon on the file in any
> file browser)
> 2. All the correct config for how to make the VM implementation start this
> image
> 3. A first-run startup message with instructions
> 4. A click-through license agreement
>
> The user would download and double-click a single file and the VM would
> start up, ask me to agree to a license, provide me the instructions on how
> to begin and just start running.

This is already broken because you're assuming a suitable version of qemu i=
s=20
preinstalled on the user's machine.  Once you have to install qemu, you can=
=20
just as easily install a frontend to provide whatever user interface you=20
want.

All modern filesystems have things called "directories" or "folders" than b=
e=20
be used to group sets of related files.

Paul