Remove $ Id $

[virt-p2v.git] / README.developers

diff --git a/README.developers b/README.developers
index f7b205e..232805e 100644 (file)
--- a/README.developers
+++ b/README.developers
@@ -1,5 +1,3 @@
-$Id$
-
 Background reading
 ----------------------------------------------------------------------
 
@@ -23,11 +21,6 @@ livecd-post.sh.in
   before the live CD is turned into an ISO.  The shell script creates
   any extra files we need on the live CD.
 
-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).
-
 virt-p2v
 
   This is the virt-p2v P2V configuration tool itself.  It is
@@ -39,6 +32,10 @@ inittab
 
   Replacement /etc/inittab.
 
+iso-attach
+
+  Attach newer virt-p2v scripts to pre-built ISOs (used by 'make update').
+
 General implementation plan
 ----------------------------------------------------------------------
 
@@ -65,23 +62,7 @@ this:
 
   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:
-
-  dd if=/dev/disk | nc xenhost port
-
-  and on the remote host they do:
-  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
 to files, and still see the "modified" block device (d).  A hairy
 script looks for candidate files to modify.
-
-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.