doc: Make explicit that ovs-vswitchd is the preferred switch.

Many people who are looking for an OpenFlow switch assume that
the only way to do it is using ovs-openflowd.  Sometimes they also
run ovs-vswitchd at the same time.  Try to clarify that neither
of these are necessary and ovs-vswitchd can handle OpenFlow by
itself and is the preferred method of doing so.

diff --git a/INSTALL.OpenFlow b/INSTALL.OpenFlow
index 7a4a7e6..684d01f 100644 (file)
--- a/INSTALL.OpenFlow
+++ b/INSTALL.OpenFlow
@@ -3,9 +3,11 @@
 
 Open vSwitch uses OpenFlow as its preferred method of remote flow
 table configuration.  This is the simplest method of using it with an
 
 Open vSwitch uses OpenFlow as its preferred method of remote flow
 table configuration.  This is the simplest method of using it with an

-OpenFlow controller.  The ovs-vsctl "set-controller" command will set
-the controller for one or more bridges.  We recommend using OpenFlow
-in this manner.
+OpenFlow controller.  The ovs-vsctl "set-controller" command can also
+be used in conjunction with ovs-vswitchd to set the controller for one
+or more bridges.  We recommend using OpenFlow in this manner and in this
+case you should not run ovs-openflowd.  Directions for setting up
+ovs-vswitchd can be found in INSTALL.Linux.

 
 However, it is also possible to use Open vSwitch as a simple OpenFlow
 switch like that provided by the OpenFlow reference implementation
 
 However, it is also possible to use Open vSwitch as a simple OpenFlow
 switch like that provided by the OpenFlow reference implementation