From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1EMA3n-0002NF-Ps
	for qemu-devel@nongnu.org; Sun, 02 Oct 2005 16:03:52 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1EMA3b-0002If-Bb
	for qemu-devel@nongnu.org; Sun, 02 Oct 2005 16:03:35 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1EMA3a-0002AS-Uy
	for qemu-devel@nongnu.org; Sun, 02 Oct 2005 16:03:34 -0400
Received: from [128.8.10.163] (helo=po1.wam.umd.edu)
	by monty-python.gnu.org with esmtp (Exim 4.34) id 1EM9nf-0005CH-Lw
	for qemu-devel@nongnu.org; Sun, 02 Oct 2005 15:47:07 -0400
Received: from jbrown.mylinuxbox.org (jma-box.student.umd.edu [129.2.253.219])
	by po1.wam.umd.edu (8.12.10/8.12.10) with ESMTP id j92Jl5jK009904
	for <qemu-devel@nongnu.org>; Sun, 2 Oct 2005 15:47:05 -0400 (EDT)
Date: Sun, 2 Oct 2005 15:47:03 -0400
From: "Jim C. Brown" <jma5@umd.edu>
Subject: Re: [Qemu-devel] tun/tap networking: patch for existing tun
Message-ID: <20051002194703.GA16244@jbrown.mylinuxbox.org>
References: <20050930221321.C7BED31C14@ravel.n2.net>
	<20050930230149.GA20433@jbrown.mylinuxbox.org>
	<433E44F9.8040501@eclis.ch>
	<20051001131215.GB28444@jbrown.mylinuxbox.org>
	<433EF5C4.2030801@eclis.ch>
	<Pine.LNX.4.61.0510020441150.21519@filer.marasystems.com>
	<433F92CB.1060600@eclis.ch>
	<Pine.LNX.4.61.0510021222170.6283@filer.marasystems.com>
	<20051002165353.GA14941@tuxedo.skovlyporten.dk>
	<43401DE5.7080402@eclis.ch>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <43401DE5.7080402@eclis.ch>
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

On Sun, Oct 02, 2005 at 07:50:29PM +0200, Jean-Christian de Rivaz wrote:
> 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
> 

If it's persistent, the device should already have been set up before qemu gets
its hands on it. Same goes for pre-created tuntaps that are passed via -tun-fd.
Only the tap devices that qemu creates need to be set up by qemu, which is the
only case where we have to have the network script.

-- 
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.