X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=INSTALL.bridge;h=b30152d4baa2b518626ab770369468a87b41ccaa;hb=03292c465464a1bb10b07ea5036ce64083984dd3;hp=ec9e0914f79e3029629aa31670009e114bff804e;hpb=5fca1acd934c87b4ea4e47ff24235343b6db3035;p=openvswitch

diff --git a/INSTALL.bridge b/INSTALL.bridge
index ec9e0914..b30152d4 100644
--- a/INSTALL.bridge
+++ b/INSTALL.bridge
@@ -4,10 +4,12 @@
 This file documents how Open vSwitch may be used as a drop-in
 replacement for a Linux kernel bridge in an environment that includes
 elements that are tightly tied to the Linux bridge tools
-(e.g. "brctl") and architecture.  We do not recommend using the
-approach described here outside such an environment, since the other
-tools included with Open vSwitch are easier to use and more
-general-purpose than the Linux bridging tools.
+(e.g. "brctl") and architecture.  We recommend directly using the
+management tools provided with Open vSwitch rather than these
+compatibility hooks for environments that are not tightly tied to the
+Linux bridging tools; they are more efficient and better reflect the
+actual operation and status.
+
 
 Installation Procedure
 ----------------------
@@ -40,10 +42,11 @@ to update system scripts to follow these steps.
    bridge interfaces), to ensure that the Open vSwitch kernel modules
    are loaded before the Linux kernel bridge module.
 
-3. Create an initial ovs-vswitchd.conf file.  This file may be empty
-   when ovs-vswitchd, or you may add any valid configuration
-   directives to it (as described in ovs-vswitchd.conf(5)), but it
-   must exist.
+3. Create an initial version of the configuration file, for example
+   /etc/ovs-vswitchd.conf.  This file may be empty initially or may
+   contain add any valid configuration directives described in
+   ovs-vswitchd.conf(5).  However, it must exist when you start
+   ovs-vswitchd.
 
    To create an empty configuration file:
 
@@ -51,8 +54,11 @@ to update system scripts to follow these steps.
 
 4. Start ovs-vswitchd and ovs-brcompatd, e.g.:
 
-      % ovs-vswitchd -P -D -vANY:console:EMER /etc/ovs-vswitchd.conf
-      % ovs-brcompatd -P -D -vANY:console:EMER /etc/ovs-vswitchd.conf
+      % ovs-vswitchd --pidfile --detach -vANY:console:EMER \
+                /etc/ovs-vswitchd.conf
+
+      % ovs-brcompatd --pidfile --detach -vANY:console:EMER \
+                /etc/ovs-vswitchd.conf
 
 5. Now you should be able to manage the Open vSwitch using brctl and
    related tools.  For example, you can create an Open vSwitch bridge,
@@ -65,10 +71,10 @@ to update system scripts to follow these steps.
       % brctl show
 
    Each of these commands actually uses or modifies the Open vSwitch
-   configuration.  For example, after executing the commands above
-   starting from an empty configuration file, "cat
-   /etc/ovs-vswitchd.conf" should show that the configuration file now
-   contains the following:
+   configuration file, then notifies the ovs-vswitchd daemon of the
+   change.  For example, after executing the commands above starting
+   from an empty configuration file, "cat /etc/ovs-vswitchd.conf"
+   should show that the configuration file now contains the following:
 
       bridge.br0.port=br0
       bridge.br0.port=eth0