Finish off first version of conversion.

[virt-p2v.git] / README.developers

diff --git a/README.developers b/README.developers
index 8dd9561..784504a 100644 (file)
--- a/README.developers
+++ b/README.developers
@@ -35,6 +35,10 @@ virt-p2v.sh
   live CD has booted.  All the P2V stuff happens from this script. It
   uses the 'dialog' program to ask questions.
 
+inittab
+
+  Replacement /etc/inittab.
+
 General implementation plan
 ----------------------------------------------------------------------
 
@@ -59,7 +63,7 @@ for devices in /sys/block.
 For (b) we can simply use 'dd' and 'ssh'.  The general plan is to do
 this:
 
-  dd if=/dev/disk | gzip | ssh xenhost 'cat > /var/lib/xen/images/disk.img'
+  dd if=/dev/disk | gzip | ssh xenhost 'zcat > /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:
@@ -67,7 +71,7 @@ also opt for a pure TCP transport:
   dd if=/dev/disk | gzip | nc xenhost port
 
   and on the remote host they do:
-  nc -l -p port > /var/lib/xen/images/disk.img
+  nc -kl port > /var/lib/xen/images/disks
 
 For (c) we can use device-mapper snapshots to mount a ramdisk above
 the disks themselves.  This allows us to make non-destructive changes
@@ -79,5 +83,5 @@ Non-generic virt-p2v
 
 The above describes the generic virt-p2v, which asks users questions
 after boot.  It is also possible to build your own live CD, based on
-virt-p2v which has various settings compiled in, so it runs
-automatically.
\ No newline at end of file
+virt-p2v, which has various settings compiled in so it runs
+automatically.