X-Git-Url: http://git.annexia.org/?a=blobdiff_plain;f=README.developers;h=02dfa6cc322019f06dbdd786f00fef5328ba5acb;hb=bdd446d592ee689fcdbbc458d7f88b4135ca557d;hp=6ba07339d13fbcf99fb443a1c112b934384bafd2;hpb=6d37b5f61c6cd4115197dc25e6d7ab571fcb3a54;p=virt-p2v.git

diff --git a/README.developers b/README.developers
index 6ba0733..02dfa6c 100644
--- a/README.developers
+++ b/README.developers
@@ -1,5 +1,3 @@
-$Id$
-
 Background reading
 ----------------------------------------------------------------------
 
@@ -10,28 +8,16 @@ About Live CDs / livecd-creator tool:
 The files in this directory
 ----------------------------------------------------------------------
 
-livecd.ks.in
+p2v.ks.in
 
   Kickstart file which describes how to build the live CD.  This is
   essentially the configuration file for livecd-creator.  Most
   importantly it lists the RPMs which are needed on the live CD.
 
-livecd-post.sh.in
-
-  This is the %post-configuration section of the Kickstart script.  It
-  is a shell script which runs after the RPMs have been installed but
-  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
 
-virt-p2v.sh
-
-  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 P2V configuration tool itself.  It is
+  installed on the live CD as /usr/bin/virt-p2v and runs after the
   live CD has booted.  All the P2V stuff happens from this script. It
   uses the 'dialog' program to ask questions.
 
@@ -39,6 +25,16 @@ inittab
 
   Replacement /etc/inittab.
 
+iso-attach
+
+  Attach newer virt-p2v scripts to pre-built ISOs (used by 'make update').
+
+extras/
+
+  Anything under here is copied onto the ISO squashfs.  In particular
+  this contains paravirt drivers for Red Hat Enterprise Linux,
+  CentOS and friends.
+
 General implementation plan
 ----------------------------------------------------------------------
 
@@ -63,25 +59,9 @@ 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'
-
-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
-
-  and on the remote host they do:
-  nc -l -p port > /var/lib/xen/images/disk.img
+  dd if=/dev/disk | ssh -C xenhost 'cat > /var/lib/xen/images/disk.img'
 
 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.
-
-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.
+script looks for candidate files to modify.