From bca38c997e70f843198b66bb537e453df260bc4c Mon Sep 17 00:00:00 2001 From: Bob Lantz Date: Sun, 14 Mar 2010 00:18:24 -0800 Subject: [PATCH] Minor config notes changes. --- INSTALL | 13 +++---------- 1 file changed, 3 insertions(+), 10 deletions(-) diff --git a/INSTALL b/INSTALL index b66944d..36b9d58 100644 --- a/INSTALL +++ b/INSTALL @@ -9,20 +9,13 @@ Preliminary Mininet Installation/Configuration Notes This places the mininet package in /usr/lib/python-2.5/site-packages/, so that 'import mininet' will work. - -- A functional netns binary is required to run mininet, but currently you - have to compile it and install it yourself from the included .c file: - to make it: make netns (or cc -o netns netns.c) - to test it: ./netns /sbin/ifconfig -a - to 'install' a link to it, you could do something like: - sudo ln -s /home/openflow/mininet/netns /usr/local/bin/netns - - Installation is simplest with a distribution that includes a kernel +- Installation is simplest with a distribution that includes a kernel which supports the CLONE_NETNS unshare flag by default. Debian 5.0+ does (e.g. current debian-testing release); Ubuntu doesn't. If your kernel doesn't support it, you will need to build and install a kernel that - does! + does! If you are using OpenVSwitch, 2.6.33 works best. For the reference + kernel switch, 2.6.30 is compatible. - Mininet should probably be run either on a machine with no other important processes, or on a virtual machine.