From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: [patch] xen udev rule interfering with openvpn Date: Fri, 20 Apr 2012 12:00:13 +0100 Message-ID: <1334919613.28331.53.camel@zakaz.uk.xensource.com> References: <1334658395.23948.6.camel@zakaz.uk.xensource.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> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20369.16555.46229.798603@mariner.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Jackson Cc: M A Young , Roger Pau Monne , Teck Choon Giam , "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org On Fri, 2012-04-20 at 11:55 +0100, Ian Jackson wrote: > Ian Campbell writes ("Re: [Xen-devel] [patch] xen udev rule interfering with openvpn"): > > On Fri, 2012-04-20 at 11:38 +0100, Ian Jackson wrote: > > > Are we > > > sure that this isn't going to break some existing setup where the name > > > is already using most of the available length ? > > > > On the contrary I'm fairly sure it will break them... How common they > > would be I can't say (other than my gut feeling being "not very"). > > > > Not sure what our options are here. Perhaps in the grant Unix tradition > > of dropping vowels and random consonants "xtp-". Or perhaps "emu-" (for > > emulated)? > > 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. Ian. > > > This still adds a new 4 char prefix in the xl case but xend already had > > that behaviour so hopefully people haven't come to rely on it in the > > meantime. > > I think that's a fair enough assumption. > > Ian.