From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FyQIy-0000tT-1G for qemu-devel@nongnu.org; Thu, 06 Jul 2006 05:37:52 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FyQIv-0000r5-U0 for qemu-devel@nongnu.org; Thu, 06 Jul 2006 05:37:51 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FyQIv-0000r2-Ox for qemu-devel@nongnu.org; Thu, 06 Jul 2006 05:37:49 -0400 Received: from [83.148.189.24] (helo=mxbackup.griffin.com) by monty-python.gnu.org with esmtp (Exim 4.52) id 1FyQJ4-0007jv-QI for qemu-devel@nongnu.org; Thu, 06 Jul 2006 05:37:59 -0400 Received: from Agape.local (82.151.249.90.adsl.griffin.net.uk [82.151.249.90]) by mxbackup.griffin.com (Postfix) with ESMTP id 0FE1910E9F17 for ; Thu, 6 Jul 2006 09:16:22 +0100 (BST) Subject: Re: [Qemu-devel] No useful documentation. From: Daniel Carrera In-Reply-To: <200607051700.35027.mikeonthecomputer@gmail.com> References: <1152133046.8295.85.camel@Agape-desktop> <20060705214643.GB21797@muon.de> <1152136920.8295.126.camel@Agape-desktop> <200607051700.35027.mikeonthecomputer@gmail.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-esAkCTQIvo9B/9juNbWz" Date: Thu, 06 Jul 2006 09:16:21 +0100 Message-Id: <1152173781.14322.3.camel@Agape-desktop> Mime-Version: 1.0 Reply-To: daniel.carrera@zmsl.com, qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org --=-esAkCTQIvo9B/9juNbWz Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Wed, 2006-05-07 at 17:00 -0700, Mike Swanson wrote: > On Wednesday 05 July 2006 15:01, Daniel Carrera wrote: > > Yes, but the doc doesn't, for example, explain how you are supposed to > > put a bootable image in "file". This is addressed by the excellent > > responses from Nathaniel and Rick, and I included it in my proposed > > tutorial. > > > > This is the sort of thing that might be obvious to you in hindsight > > (you're very involved in qemu) but won't be to a lot of people who are > > technically competent, but don't already know qemu. >=20 > It doesn't require any involvement to understand, I didn't say it required involvement to understand. I understand it now, and it only took 1 sentence to explain it. But that sentence really has to be in the documentation, and where it can be found. You are confusing complexity with poor documentation. Qemu is not hard to use, it is poorly documented. Big difference. The way qemu works is not at all obvious, it needs to be explained, even if the explanation only takes 1 paragraph. Cheers, Daniel. --=20 http://opendocumentfellowship.org "The reasonable man adapts himself to the world; the unreasonable man tries to adapt the world to himself. Therefore all progress depends on unreasonable men." -- George Bernard Shaw --=-esAkCTQIvo9B/9juNbWz Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQBErMbVp0IZBOPRtlQRAhzWAKCiQskB1gy1rpwYaYH62PpVESezGQCeO7kd zFYbJIdg4OQA52X41JaWVu0= =q+5w -----END PGP SIGNATURE----- --=-esAkCTQIvo9B/9juNbWz--