[Pkg-vsquare-changes] r124 - vde2/trunk/debian

[filippo at alioth.debian.org]

Author: filippo
Date: 2008-02-18 17:26:48 +0000 (Mon, 18 Feb 2008)
New Revision: 124

Modified:
   vde2/trunk/debian/README.Debian
   vde2/trunk/debian/changelog
Log:
* Expand and spell-check README.Debian, add manual method example
(Closes: #466363)

Modified: vde2/trunk/debian/README.Debian
===================================================================
--- vde2/trunk/debian/README.Debian	2008-02-07 17:28:00 UTC (rev 123)
+++ vde2/trunk/debian/README.Debian	2008-02-18 17:26:48 UTC (rev 124)
@@ -11,11 +11,11 @@
       Start TAP interface with vde_switch command which has control directory
       /var/run/vde/$IFACE.ctl. The control directory is writable by vde2-net
       group. The additional parameters might be --macaddr MAC for switch MAC
-      address or other parameters. Call `vde_switch --help' for description.
+	  address or other parameters. See `vde_switch --help' or vde_switch(1) for
+	  description.
 
-	  When using the "manual" method of ifupdown no TAP interface will be
-	  attached to the switch, instead only unix socket connectivity will be
-	  present, e.g.:
+	  When using the "manual" method of ifupdown no further setup is made, thus
+	  it is possible to connect only the unix socket, e.g.:
 		
 	  auto vde0
 	  iface vde0 inet manual
@@ -25,6 +25,13 @@
 	  In this case vde0 is used for future reference, for example management
 	  socket can be accessed from /var/run/vde2/vde0.mgmt
 
+	  It might be also convenient to attach a vde2-switch to a tap on boot to
+	  use for bridging:
+
+	  auto qemu
+	  iface qemu inet manual
+	  	vde2-switch -t qemu
+		  
     * vde2-slirp -|<parameters>
 
       Start slirp interface connected to the VDE switch with slirpvde command.
@@ -36,14 +43,14 @@
       Slirp does not require root access, kernel ip forwarding or iptables
       configuration. Tap requires root access, provide any kind of routing
       as it were a real interface and it is faster.
-      Do not use tap and slirp together in the same VDE LAN provided 
-      you know exactly what you are doing. If you set up a slirp with dhcp
+      Do not use tap and slirp together in the same VDE LAN unless 
+      you know exactly what you are doing. If you set up a slirp with DHCP
       on a tap and you autoconfigure the interface it will become the
       default route for the entire system.
       
     * vde2-plug <dpipe_arg2>
     
-      Start VDE plug to be connected into a VDE switch controlled by TAP device
+      Start a VDE plug to be connected to a VDE switch controlled by TAP device
       and other switch called by second argument of dpipe command.
       
       i.e.
@@ -248,7 +255,7 @@
    (see slirpvde man page for further details).
 
   Management console
-  -----------------
+  ------------------
 
   You can connect to remote console with unixterm command:
   
@@ -258,4 +265,3 @@
 
   -- Piotr Roszatycki <dexter at debian.org>  Thu, 14 Dec 2006 10:22:19 +0100
   -- Renzo Davoli <renzo at cs.unibo.it>  Fri Apr 20 19:33:27 +0200
-

Modified: vde2/trunk/debian/changelog
===================================================================
--- vde2/trunk/debian/changelog	2008-02-07 17:28:00 UTC (rev 123)
+++ vde2/trunk/debian/changelog	2008-02-18 17:26:48 UTC (rev 124)
@@ -1,8 +1,10 @@
 vde2 (2.2.0-pre2-2) UNRELEASED; urgency=low
 
   * Suggest: qemu and kvm as requested in #461514
+  * Expand and spell-check README.Debian, add manual method example
+  (Closes: #466363)
 
- -- Filippo Giunchedi <filippo at debian.org>  Wed, 06 Feb 2008 22:14:41 +0100
+ -- Filippo Giunchedi <filippo at debian.org>  Mon, 18 Feb 2008 18:26:04 +0100
 
 vde2 (2.2.0-pre2-1) unstable; urgency=low