From: "Alexey Eremenko" <al4321@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: Re[2]: [Qemu-devel] Poor Qemu documentation for Windows host
Date: Wed, 20 Sep 2006 16:20:53 -0200 [thread overview]
Message-ID: <7fac565a0609201120q3a80a342k74316e3a238c173c@mail.gmail.com> (raw)
In-Reply-To: <489863085.20060919025017@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 207 bytes --]
Hi all again!
OK, I have updated the docs, and made a patch.
Please update the docs on site.
patch attached in this email. (don't know if it's filetered.... if you have
problems with filters let me know.)
[-- Attachment #1.2: Type: text/html, Size: 228 bytes --]
[-- Attachment #2: qemu-doc-modi02.diff --]
[-- Type: text/x-patch, Size: 2170 bytes --]
--- qemu-doc.html 2006-07-24 23:13:00.000000000 -0200
+++ qemu-doc-modi02.html 2006-09-20 21:16:52.000000000 -0200
@@ -11,10 +11,10 @@
-->
<head>
-<title>QEMU CPU Emulator User Documentation: </title>
+<title>QEMU System Emulator User Documentation: </title>
-<meta name="description" content="QEMU CPU Emulator User Documentation: ">
-<meta name="keywords" content="QEMU CPU Emulator User Documentation: ">
+<meta name="description" content="QEMU System Emulator User Documentation: ">
+<meta name="keywords" content="QEMU System Emulator User Documentation: ">
<meta name="resource-type" content="document">
<meta name="distribution" content="global">
<meta name="Generator" content="texi2html 1.68">
@@ -46,7 +46,7 @@
<td valign="middle" align="left">[<a href="#SEC59" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
-<h1 class="settitle">QEMU CPU Emulator User Documentation
+<h1 class="settitle">QEMU System Emulator User Documentation
</h1>
@@ -1457,7 +1457,7 @@
a virtual network device on your host (called <code>tapN</code>), and you
can then configure it as if it was a real ethernet card.
-</p><p>As an example, you can download the `<tt>linux-test-xxx.tar.gz</tt>'
+</p><p>[Linux only] As an example, you can download the `<tt>linux-test-xxx.tar.gz</tt>'
archive and copy the script `<tt>qemu-ifup</tt>' in `<tt>/etc</tt>' and
configure properly <code>sudo</code> so that the command <code>ifconfig</code>
contained in `<tt>qemu-ifup</tt>' can be executed as root. You must verify
@@ -1468,6 +1468,12 @@
Linux distribution and <a href="#SEC10">Invocation</a> to have examples of
command lines using the TAP network interfaces.
+<p>[Windows only] There is a virtual ethernet driver for Windows
+2000/XP systems, called TAP-Win32. But it is not included in standard
+Qemu for Windows, so you will need to get it separately. It is part of
+OpenVPN package, so download OpenVPN from : <a href="http://openvpn.net/">http://openvpn.net/</a> .</p>
+
+
</p><hr size="6">
<a name="SEC23"></a>
<table cellpadding="1" cellspacing="1" border="0">
next prev parent reply other threads:[~2006-09-20 18:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-18 3:05 [Qemu-devel] Poor Qemu documentation for Windows host Alexey Eremenko
2006-09-18 3:15 ` Lonnie Mendez
2006-09-18 19:17 ` Alexey Eremenko
2006-09-18 20:33 ` Alexey Eremenko
2006-09-18 23:50 ` Re[2]: " Paul Sokolovsky
2006-09-20 18:20 ` Alexey Eremenko [this message]
2006-09-20 18:48 ` Alexey Eremenko
2006-09-21 16:46 ` Alexey Eremenko
2006-09-22 10:15 ` Jan Marten Simons
2006-09-18 17:48 ` Dirk Behme
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=7fac565a0609201120q3a80a342k74316e3a238c173c@mail.gmail.com \
--to=al4321@gmail.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).