Bumped version number.

[virt-p2v.git] / README.developers

diff --git a/README.developers b/README.developers
index 784504a..b7082f3 100644 (file)
--- a/README.developers
+++ b/README.developers
@@ -28,10 +28,10 @@ p2v.init
   This is installed on the live CD as /etc/init.d/p2v, and it causes the
   live CD to boot into the P2V configuration tool (see next).
 
   This is installed on the live CD as /etc/init.d/p2v, and it causes the
   live CD to boot into the P2V configuration tool (see next).
 

-virt-p2v.sh
+virt-p2v.ml

 
 

-  This is the virt-p2v.sh P2V configuration tool itself.  It is
-  installed on the live CD as /usr/bin/virt-p2v.sh and runs after the
+  This is the virt-p2v.ml P2V configuration tool itself.  It is
+  installed on the live CD as /usr/bin/virt-p2v.ml and runs after the

   live CD has booted.  All the P2V stuff happens from this script. It
   uses the 'dialog' program to ask questions.
 
   live CD has booted.  All the P2V stuff happens from this script. It
   uses the 'dialog' program to ask questions.
 


@@ -63,12 +63,12 @@ for devices in /sys/block.
 For (b) we can simply use 'dd' and 'ssh'.  The general plan is to do
 this:
 
 For (b) we can simply use 'dd' and 'ssh'.  The general plan is to do
 this:
 

-  dd if=/dev/disk | gzip | ssh xenhost 'zcat > /var/lib/xen/images/disk.img'
+  dd if=/dev/disk | ssh -C xenhost 'cat > /var/lib/xen/images/disk.img'

 
 If the user doesn't have sshd installed on the Xen host, then they can
 also opt for a pure TCP transport:
 
 
 If the user doesn't have sshd installed on the Xen host, then they can
 also opt for a pure TCP transport:
 

-  dd if=/dev/disk | gzip | nc xenhost port
+  dd if=/dev/disk | nc xenhost port

 
   and on the remote host they do:
   nc -kl port > /var/lib/xen/images/disks
 
   and on the remote host they do:
   nc -kl port > /var/lib/xen/images/disks


@@ -76,7 +76,7 @@ also opt for a pure TCP transport:
 For (c) we can use device-mapper snapshots to mount a ramdisk above
 the disks themselves.  This allows us to make non-destructive changes
 to files, and still see the "modified" block device (d).  A hairy
 For (c) we can use device-mapper snapshots to mount a ramdisk above
 the disks themselves.  This allows us to make non-destructive changes
 to files, and still see the "modified" block device (d).  A hairy

-shell script looks for candidate files to modify.
+script looks for candidate files to modify.

 
 Non-generic virt-p2v
 ----------------------------------------------------------------------
 
 Non-generic virt-p2v
 ----------------------------------------------------------------------