From: Ian Campbell <Ian.Campbell@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Roger Pau Monne <roger.pau@citrix.com>,
Teck Choon Giam <giamteckchoon@gmail.com>,
M A Young <m.a.young@durham.ac.uk>
Subject: Re: [patch] xen udev rule interfering with openvpn
Date: Wed, 25 Apr 2012 11:14:40 +0100 [thread overview]
Message-ID: <1335348880.28015.24.camel@zakaz.uk.xensource.com> (raw)
In-Reply-To: <20375.52677.287182.934829@mariner.uk.xensource.com>
On Wed, 2012-04-25 at 11:11 +0100, Ian Jackson wrote:
> Ian Campbell writes ("Re: [Xen-devel] [patch] xen udev rule interfering with openvpn"):
> > So for vifname="foo" it is a no-brainer to call the vif "foo" and the
> > emulated tap device "foo-emu".
> >
> > But what about the case where no vifname is given, in that case vif is
> > named "vif<DOM>.<DEV>". But what to call the tap? Previously I was
> > changing the name from tap<DOM>.<DEV> to xentap<DOM>.<DEV> but perhaps
> > now "vif<DOM>.<DEV>-emu" makes more sense/is more consistent?
>
> I think either is fine. While we're changing it it probably makes
> sense to use "vif..." as indeed it is more consistent.
OK, vifX.Y and vifX.Y-emu it is...
Ian.
next prev parent reply other threads:[~2012-04-25 10:14 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-16 19:03 [patch] xen udev rule interfering with openvpn M A Young
2012-04-17 10:26 ` Ian Campbell
2012-04-17 13:08 ` Roger Pau Monne
2012-04-18 18:25 ` Teck Choon Giam
2012-04-19 6:39 ` Ian Campbell
2012-04-20 9:03 ` Ian Campbell
2012-04-20 10:38 ` Ian Jackson
2012-04-20 10:48 ` Ian Campbell
2012-04-20 10:55 ` Ian Jackson
2012-04-20 11:00 ` Ian Campbell
2012-04-20 11:04 ` Ian Jackson
2012-04-20 13:21 ` Ian Campbell
2012-04-20 15:26 ` Teck Choon Giam
2012-04-20 15:38 ` Ian Campbell
2012-04-20 16:34 ` Teck Choon Giam
2012-04-25 9:59 ` Ian Campbell
2012-04-25 10:11 ` Ian Jackson
2012-04-25 10:14 ` Ian Campbell [this message]
2012-04-25 12:58 ` Ian Campbell
2012-04-25 13:16 ` Roger Pau Monne
2012-04-25 13:38 ` Ian Campbell
2012-05-11 14:53 ` Ian Jackson
2012-05-11 23:53 ` Teck Choon Giam
2012-05-12 7:29 ` Teck Choon Giam
2012-05-12 22:00 ` Teck Choon Giam
2012-05-12 22:30 ` Ian Campbell
2012-05-12 23:37 ` Teck Choon Giam
2012-05-13 0:39 ` Teck Choon Giam
2012-05-21 12:31 ` Ian Campbell
2012-05-21 12:51 ` Teck Choon Giam
2012-05-21 13:04 ` Ian Campbell
2012-05-21 13:16 ` Teck Choon Giam
2012-05-22 13:19 ` Ian Campbell
2012-05-23 2:22 ` Teck Choon Giam
2012-05-23 9:37 ` Ian Campbell
2012-05-23 13:04 ` Teck Choon Giam
2012-05-23 14:54 ` Teck Choon Giam
2012-05-21 12:24 ` Teck Choon Giam
2012-05-21 12:49 ` Ian Campbell
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=1335348880.28015.24.camel@zakaz.uk.xensource.com \
--to=ian.campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=giamteckchoon@gmail.com \
--cc=m.a.young@durham.ac.uk \
--cc=roger.pau@citrix.com \
--cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.