Search Mailing List Archives
[mininet-discuss] How to change source code and Openswitch version?
rlantz at cs.stanford.edu
Sat Jul 1 15:49:22 PDT 2017
Usually you shouldn't need to change the Mininet source code at all - just subclass it!!
Also, assertions are there for a reason!! They indicate conditions that should never occur - in your example, invoking a non-reentrant API from multiple threads (as I noted, it's not a sensible thing for multiple threads to send commands to a single shell process - that's not the way bash works!!)
The build directory is for the easy_install/setup.py packaging, but most of the time you shouldn't have to worry about it.
If you absolutely need to change the Mininet code (for example to prepare a bug fix or pull request) you can use "make develop" to link the source tree into the Python library directories so you can use it live without having to install it (which you can also do using "make install" assuming all of the prereqs are installed.)
> On Jul 1, 2017, at 3:13 PM, Yu Hao <jimmy19940111 at gmail.com> wrote:
> Hello, I'm new to the mininet and I got some problems:
> 1. How could I change the mininet source code?
> I got error like this:
> File "build/bdist.linux-x86_64/egg/mininet/node.py", line 355, in cmd
> self.sendCmd( *args, **kwargs )
> File "build/bdist.linux-x86_64/egg/mininet/node.py", line 272, in sendCmd
> assert self.shell and not self.waiting
> I want to change one line in the node.py file, but it doesn't work (it seems the code has not been updated).
> So I changed two files in the mininet
> And I also generated a new .pyc file for each of them.
> It still doesn't work.
> The weirdest part is that the dir 'build/bdist.linux-x86_64/' is empty and why would I get error like this?
> This file is even empty when the process is running.
> 2. The current version of switch in the mininet only supports Openflow 1.3, is it possible to update the switch which support Openflow 1.5?
> Could Anyone help me with that?
> Thanks in advance!
> mininet-discuss mailing list
> mininet-discuss at lists.stanford.edu
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the mininet-discuss