From: Jean-Christian de Rivaz <jc@eclis.ch>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] tun/tap networking: patch for existing tun
Date: Sun, 02 Oct 2005 19:50:29 +0200 [thread overview]
Message-ID: <43401DE5.7080402@eclis.ch> (raw)
In-Reply-To: <20051002165353.GA14941@tuxedo.skovlyporten.dk>
Lars Munch a écrit :
> On Sun, Oct 02, 2005 at 12:24:53PM +0200, Henrik Nordstrom wrote:
>
>>On Sun, 2 Oct 2005, Jean-Christian de Rivaz wrote:
>>
>>
>>>Yes. This is just an update of my first patch posted the 13 january 2005
>>>so it should apply without offset warning.
>>>
>>>Maybe can I propose to joint our effort ?
>>
>>What remains to make it complete is the command line parser, allowing
>>network options to be specified in a reasonable manner. See discussions
>>some time ago regarding MAC addresses.
>>
>>Regards
>>Henrik
>
>
> The "use existing tun/tap network interface" is is a popular patch to
> create. I also did one in november 2004 :-)
>
> http://lists.gnu.org/archive/html/qemu-devel/2004-11/msg00454.html
Good to know that (I joined the liste only this year).
It's nice to see that we all have almost the same idea of how to do the
patch. As I see, there just differ in some details and in how to handle
the network script.
Is there any guideline about the network script ? Or should we add an
option to let the choice to the user if the network script is called or
not ?
--
Jean-Christian de Rivaz
next prev parent reply other threads:[~2005-10-02 18:10 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-30 22:13 [Qemu-devel] tun/tap networking Don Kitchen
2005-09-30 22:21 ` Henrik Nordstrom
2005-09-30 22:21 ` Paul Brook
2005-09-30 23:01 ` Jim C. Brown
2005-10-01 8:12 ` Jean-Christian de Rivaz
2005-10-01 13:12 ` Jim C. Brown
2005-10-01 20:24 ` Jean-Christian de Rivaz
2005-10-01 21:09 ` Jim C. Brown
2005-10-01 21:17 ` Jean-Christian de Rivaz
2005-10-01 20:47 ` [Qemu-devel] tun/tap networking: patch for existing tun Jean-Christian de Rivaz
2005-10-02 2:42 ` Henrik Nordstrom
2005-10-02 7:56 ` Jean-Christian de Rivaz
2005-10-02 10:24 ` Henrik Nordstrom
2005-10-02 16:53 ` Lars Munch
2005-10-02 17:50 ` Jean-Christian de Rivaz [this message]
2005-10-02 19:47 ` Jim C. Brown
2005-10-02 20:27 ` Jean-Christian de Rivaz
2005-10-02 18:45 ` Anthony Liguori
2005-10-02 19:39 ` Jim C. Brown
2005-10-02 20:23 ` Jean-Christian de Rivaz
2005-10-02 22:37 ` Jim C. Brown
2005-10-03 9:46 ` Jean-Christian de Rivaz
2005-10-03 12:04 ` Jim C. Brown
2005-10-03 13:10 ` Jean-Christian de Rivaz
2005-10-03 13:19 ` Henrik Nordstrom
2005-10-03 13:13 ` Henrik Nordstrom
2005-10-03 14:14 ` Jean-Christian de Rivaz
2005-10-03 13:07 ` Henrik Nordstrom
2005-10-03 14:00 ` Jean-Christian de Rivaz
2005-10-03 15:04 ` Jim C. Brown
2005-10-03 13:01 ` Henrik Nordstrom
2005-10-03 13:58 ` Jean-Christian de Rivaz
2005-10-03 15:06 ` Jim C. Brown
2005-10-03 12:54 ` Henrik Nordstrom
2005-10-03 15:14 ` Jim C. Brown
2005-10-03 18:29 ` Fabrice Bellard
2005-10-03 19:22 ` Christian MICHON
2005-10-03 20:29 ` Jean-Christian de Rivaz
2005-10-04 7:09 ` Christian MICHON
2005-10-04 7:56 ` Jean-Christian de Rivaz
2005-10-03 21:36 ` Jim C. Brown
2005-10-04 8:23 ` Matteo
2005-10-04 11:34 ` Jim C. Brown
2005-10-01 17:49 ` [Qemu-devel] tun/tap networking Henrik Nordstrom
2005-10-01 20:54 ` Jean-Christian de Rivaz
2005-10-01 11:30 ` Oliver Gerlich
2005-10-01 13:07 ` Jim C. Brown
2005-10-01 13:50 ` Paul Brook
2005-10-01 21:15 ` Jim C. Brown
2005-10-02 2:21 ` Henrik Nordstrom
2005-10-01 17:52 ` Henrik Nordstrom
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=43401DE5.7080402@eclis.ch \
--to=jc@eclis.ch \
--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).