From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: [patch] xen udev rule interfering with openvpn
Date: Fri, 20 Apr 2012 14:21:55 +0100
Message-ID: <1334928115.28331.81.camel@zakaz.uk.xensource.com>
References: <alpine.DEB.2.00.1204141534100.30192@vega-b.dur.ac.uk>
	<1334658395.23948.6.camel@zakaz.uk.xensource.com>
	<CAEwRVpP47=mKrcZ_5ATZga4wvkMaSysPh-BEfRorcxrCJ7W6pg@mail.gmail.com>
	<1334817587.11493.44.camel@dagon.hellion.org.uk>
	<1334912603.28331.2.camel@zakaz.uk.xensource.com>
	<20369.15528.270106.567037@mariner.uk.xensource.com>
	<1334918900.28331.47.camel@zakaz.uk.xensource.com>
	<20369.16555.46229.798603@mariner.uk.xensource.com>
	<1334919613.28331.53.camel@zakaz.uk.xensource.com>
	<20369.17085.330843.561841@mariner.uk.xensource.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <20369.17085.330843.561841@mariner.uk.xensource.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: M A Young <m.a.young@durham.ac.uk>, Roger Pau Monne <roger.pau@citrix.com>, Teck Choon Giam <giamteckchoon@gmail.com>, "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
List-Id: xen-devel@lists.xenproject.org

On Fri, 2012-04-20 at 12:04 +0100, Ian Jackson wrote:
> Ian Campbell writes ("Re: [Xen-devel] [patch] xen udev rule interfering with openvpn"):
> > On Fri, 2012-04-20 at 11:55 +0100, Ian Jackson wrote:
> > > I'm not quite up to speed with all the context here but is the reason
> > > that you're not suggesting "xen-" is that that's already used for
> > > something else ?
> > 
> > This is to distinguish the vif device from the associated tap device,
> > which would otherwise both be called whatever the user gave as "vifname"
> > in their config, so for vifname=foo you would get foo (the PV one) and
> > xen-foo (the EMU one) which does the job but doesn't really distinguish
> > them.
> 
> Ah, I see.  This sounds like more a job for a suffix than a prefix so
> if we can spare 4 chars I would suggest foo-emu.

I agree.

This patch interacts a bit with Roger's hotplug series, I'll rebase on
top of his with this change when he reposts it.

Ian.