All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nivedita Singhvi <niv@us.ibm.com>
To: Xen development list <xen-devel@lists.xensource.com>
Subject: Reverting bridge/antispoofing param removal
Date: Fri, 28 Oct 2005 01:14:18 -0700	[thread overview]
Message-ID: <4361DDDA.7070600@us.ibm.com> (raw)

While cleaning up some other stuff in this area, I looked
into a problem Sean Dague ran into - he was specifying br0
as the bridge name in xend-config.spx and it was still using
the original default xenbr0.  When the bridge name is
specified in the network-bridge script, it is created
correctly (ditto anti-spoofing).

A recent patchset:
http://lists.xensource.com/archives/html/xen-changelog/2005-10/msg00305.html

removed the parameters vif-bridge and anti-spoofing from
the xend/vifctl.py as the script was allowing them
to be configured.

The config file still has the examples, however, which
results in the user setting those parameters in
xend-config.spx futilely.  The actual parameter that is
used is the default (unless overridden in the script).
The intent seems to be to allow the user to configure
it in the script, and avoid the redundancy of overriding
via xend.

Would you rather have a patch that removes the example
from the xend-config.spx script, so as not to confuse the
user (but this would need sanitizing xend to use the right
params) or restore the original piece of code? It latter
worked well before, you could set it in one place and
have it be seen by script and xend.

I had both in test, will send off whichever is
desirable when I get in tmrw..

thanks,
Nivedita

                 reply	other threads:[~2005-10-28  8:14 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4361DDDA.7070600@us.ibm.com \
    --to=niv@us.ibm.com \
    --cc=xen-devel@lists.xensource.com \
    /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.