qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jamie Lokier <jamie@shareable.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] No useful documentation.
Date: Wed, 5 Jul 2006 23:30:43 +0100	[thread overview]
Message-ID: <20060705223043.GB29219@mail.shareable.org> (raw)
In-Reply-To: <20060705214643.GB21797@muon.de>

Udo 'Robos' Puetz wrote:
> -hda file
> -hdb file 
> -hdc file 
> -hdd file 
> Use file as hard disk 0, 1, 2 or 3 image (see section 3.6 Disk Images). 
> -cdrom file 
> Use file as CD-ROM image (you cannot use -hdc' and and -cdrom' at the same
> time). You can use the host CD-ROM by using /dev/cdrom' as filename. 
> -boot [a|c|d] 
> Boot on floppy (a), hard disk (c) or CD-ROM (d). Hard disk boot is the
> default.
> 
> That's in the first quarter of a medium long page and not really much
> technical gibberish before that. What more does a thinking man need? 
> I *guess* you, daniel, would have liked something where you had it all
> pre-chewed so that you don't have to read.

No, I'm guessing that concepts like "use file as a hard disk image"
and "use file as CD-ROM image" and "boot on floppy/disk/CD-ROM (does
that mean the _real_ floppy etc.?)" are alien to him, just as much as
they are second nature to us.  He just wants to run Windows apps,
remember; his interest in virtual machines probably isn't even
slightly technical.

> but keep myself from insulting people who work for free and in their
> free time!!

Indeed, the first post started with an insult and ended with a
one-sided demand "write this for me".  That's not on, from someone who
isn't paying, to _tell_ people to give up their personal time for free.

-- Jamie

  parent reply	other threads:[~2006-07-05 22:30 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
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 [this message]
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=20060705223043.GB29219@mail.shareable.org \
    --to=jamie@shareable.org \
    --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).