rename directory

diff --git a/media/lpc-2009-network-namespaces/hcalendar.html b/media/lpc-2009-network-namespaces/hcalendar.html
deleted file mode 100644 (file)
index c402336..0000000
--- a/media/lpc-2009-network-namespaces/hcalendar.html
+++ /dev/null
@@ -1,27 +0,0 @@
-<!-- http://microformats.org/wiki/hcalendar -->
-<div class="vevent">
- <span class="organiser">Pavel Emelyanov</span>
- <span class="summary">
- Why network namespace sucks and how to make it suck faster
- </span>
- <br>
- <a class="url" href="http://linuxplumbersconf.org/ocw/proposals/81">Linux Plumbers Conference</a>,
- <span class="location">Portland, OR</span>,
- <abbr class="dtstart" title="2009-09-23">Wednesday, September 23, 2009 from 10:30 – 10:55am</span>
- <div class="description">
-  The talk outlines various ways of establishing a networking
-communication between a network namespace (a container)
-and the outer world, compares their performance and features.
-<br>
-Each namespace implements its own isolated network stack.
-Network packets comes to a network stack from network device.
-Five different device types that can be used as a packets
-sources for containers are demonstrated. Their properties
-(mostly performance and maintainability) and features are
-compared.
-<br>
-In addition, one more device type is described — the one that is currently
-only implemented in the OpenVZ containers. Its pros and cons,
-and ways it can be implemented in the mainline kernel are discussed.
- </div>
-</div>

diff --git a/media/lpc-2009-network-namespaces/www b/media/lpc-2009-network-namespaces/www
deleted file mode 100644 (file)
index a0b7c1f..0000000
--- a/media/lpc-2009-network-namespaces/www
+++ /dev/null
@@ -1,5 +0,0 @@
-http://openvz.org/
-http://linuxplumbersconf.org/ocw/proposals/81
-http://video.linuxfoundation.org/video/1574
-http://podcasts.linux-foundation.org/flv/LPC2009/Pavel%20Emelyanov.flv
-http://podcasts.linux-foundation.org/ogg/LPC2009/Pavel%20Emelyanov.ogg

diff --git a/media/lpc2009-Network_namespaces/hcalendar.html b/media/lpc2009-Network_namespaces/hcalendar.html
new file mode 100644 (file)
index 0000000..c402336
--- /dev/null
+++ b/media/lpc2009-Network_namespaces/hcalendar.html
@@ -0,0 +1,27 @@
+<!-- http://microformats.org/wiki/hcalendar -->
+<div class="vevent">
+ <span class="organiser">Pavel Emelyanov</span>
+ <span class="summary">
+ Why network namespace sucks and how to make it suck faster
+ </span>
+ <br>
+ <a class="url" href="http://linuxplumbersconf.org/ocw/proposals/81">Linux Plumbers Conference</a>,
+ <span class="location">Portland, OR</span>,
+ <abbr class="dtstart" title="2009-09-23">Wednesday, September 23, 2009 from 10:30 – 10:55am</span>
+ <div class="description">
+  The talk outlines various ways of establishing a networking
+communication between a network namespace (a container)
+and the outer world, compares their performance and features.
+<br>
+Each namespace implements its own isolated network stack.
+Network packets comes to a network stack from network device.
+Five different device types that can be used as a packets
+sources for containers are demonstrated. Their properties
+(mostly performance and maintainability) and features are
+compared.
+<br>
+In addition, one more device type is described — the one that is currently
+only implemented in the OpenVZ containers. Its pros and cons,
+and ways it can be implemented in the mainline kernel are discussed.
+ </div>
+</div>

diff --git a/media/lpc2009-Network_namespaces/www b/media/lpc2009-Network_namespaces/www
new file mode 100644 (file)
index 0000000..a0b7c1f
--- /dev/null
+++ b/media/lpc2009-Network_namespaces/www
@@ -0,0 +1,5 @@
+http://openvz.org/
+http://linuxplumbersconf.org/ocw/proposals/81
+http://video.linuxfoundation.org/video/1574
+http://podcasts.linux-foundation.org/flv/LPC2009/Pavel%20Emelyanov.flv
+http://podcasts.linux-foundation.org/ogg/LPC2009/Pavel%20Emelyanov.ogg