qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Carrera <daniel.carrera@zmsl.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] No useful documentation.
Date: Wed, 05 Jul 2006 22:19:23 +0100	[thread overview]
Message-ID: <1152134363.8295.94.camel@Agape-desktop> (raw)
In-Reply-To: <1152133925.27974.4.camel@localhost.localdomain>

[-- Attachment #1: Type: text/plain, Size: 1226 bytes --]

On Wed, 2006-05-07 at 17:12 -0400, Nathaniel McCallum wrote:
> A person who is in your position (frustrated for lack of documentation)
> is actually the most qualified person to write documentation.  Feel free
> to ask any questions you have on this list.

I would be happy to contribute a section. First I need to learn how qemu
works though. Just the basics. On another list someone told me that the
way qemu works is by first creating a blank image, then booting a CD
from the virtual machine and installing.

At this point I know how to make a blank image, and I know how to boot a
CD:

qemu -cdrom /dev/cdrom

Now I need to figure out how to put these together so that if this CD
can install an operating system, qemu will know to use the blank image I
made (call it c.img) as a hard drive for its virtual machine.

Could someone tell me how to do that?

I'll be happy to write an intro tutorial for new users with the
knowledge I gain.

Cheers,
Daniel.
-- 
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

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 191 bytes --]

  reply	other threads:[~2006-07-05 21:19 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-05 20:57 [Qemu-devel] No useful documentation Daniel Carrera
2006-07-05 21:07 ` Rick Vernam
2006-07-05 21:12 ` Nathaniel McCallum
2006-07-05 21:19   ` Daniel Carrera [this message]
2006-07-05 21:25     ` Rick Vernam
2006-07-05 21:40       ` Daniel Carrera
2006-07-05 22:48         ` Flavio Visentin
2006-07-05 22:52           ` Daniel Carrera
2006-07-05 23:11             ` benb
2006-07-05 23:02               ` WaxDragon
2006-07-05 23:06           ` benb
2006-07-05 23:36             ` Flavio Visentin
2006-07-06  0:19               ` benb
2006-07-05 21:29     ` Nathaniel McCallum
2006-07-05 21:31     ` Larry Brigman
2006-07-05 21:25 ` Jamie Lokier
2006-07-05 21:38   ` Daniel Carrera
2006-07-05 22:25     ` Jamie Lokier
2006-07-05 22:45       ` benb
2006-07-05 22:41     ` NyOS
2006-07-05 21:34 ` benb
2006-07-05 21:22   ` Daniel Carrera
2006-07-05 21:46     ` Udo 'Robos' Puetz
2006-07-05 22:01       ` Daniel Carrera
2006-07-06  0:00         ` Mike Swanson
2006-07-06  8:16           ` Daniel Carrera
2006-07-06 11:03             ` denis.scheidt
2006-07-05 22:30       ` Jamie Lokier
2006-07-05 22:34 ` Ronnie Misra
2006-07-05 22:38   ` Daniel Carrera
2006-07-05 22:56     ` benb
2006-07-09  9:26 ` [Qemu-devel] " Emmanuel Charpentier
  -- strict thread matches above, loose matches on Subject: below --
2006-07-05 21:05 [Qemu-devel] " Dugger, Donald D

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=1152134363.8295.94.camel@Agape-desktop \
    --to=daniel.carrera@zmsl.com \
    --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).