[or-cvs] r19681: {torvm} Update HACKING and TODO documentation. (torvm/trunk)

[coderman@xxxxxxxx]

Author: coderman
Date: 2009-06-09 12:09:43 -0400 (Tue, 09 Jun 2009)
New Revision: 19681

Modified:
   torvm/trunk/HACKING
   torvm/trunk/TODO
Log:
Update HACKING and TODO documentation.

Modified: torvm/trunk/HACKING
===================================================================
--- torvm/trunk/HACKING	2009-06-09 15:45:19 UTC (rev 19680)
+++ torvm/trunk/HACKING	2009-06-09 16:09:43 UTC (rev 19681)
@@ -36,17 +36,6 @@
 
 
 
-If you have trouble with the build process downloading the various sources
-from mirrors and upstream repositories a current copy of all the kamikaze and
-win32 archives is available as: http://peertech.org/files/torvmdlcache.tar
-
-The extracted dl and wdl directories can be used in the build by passing their
-location to the make command:
-
-    make DLDIR=./dl WDLDIR=./wdl all
-
-
-
 Some files and paths of interest:
 
 ./build/kamikaze/x86-uclibc-vm/bin/openwrt-x86-vmlinuz
@@ -55,6 +44,7 @@
 ./build/win32/w32build.iso
 > this is the automated win32 build ISO for Qemu.  Once everything is built
 > the Qemu program and libraries will be placed in C:\Tor_VM
+> Packaged bundles and installers are saved in C:\Tor_Win32
 
 ./build/kamikaze/patches/
 > this directory contains the patch set applied to the kamikaze distribution
@@ -69,8 +59,14 @@
 > support via WinPcap and modifications for the WinPcap and TAP-Win32 drivers
 > to prevent collision with any existing installed packages.
 
+./build/kamikaze/ipv6-advnet-patches/
+> copy these files over the default patches/ to build a Tor VM kernel with
+> IPv6, advanced filtering and shaping capabilities, kernel crypto support
+> for IPsec and a number of different TCP/SCTP/misc protocols. for testing
+> experimentation only!
 
 
+
 Fully automated builds are supported with some minor modifications to both the
 Linux build host and the win32 build VM.  There are three steps to this setup:
 
@@ -88,14 +84,12 @@
 commands are invoked during build to launch the win32 build VM and have the
 completed build files copied back out to the host.  For example:
 
-    make DLDIR=/var/build/dl WDLDIR=/var/build/wdl  \
-         W32AUTO_BUILD_CMD=/var/build/runbldvm.sh   \
+    make W32AUTO_BUILD_CMD=/var/build/runbldvm.sh   \
          AUTO_SHUTDOWN=TRUE                         \
          BUILD_SCP_IDF=/var/build/build_id_rsa      \
          BUILD_SCP_USER=build                       \
          BUILD_SCP_HOST=192.168.1.2                 \
-         BUILD_SCP_DIR=/home/build                  \
-         all
+         BUILD_SCP_DIR=/home/build
 
 When the build completes a Tor_VM_<timestamp> directory will be created in the
 requested location.  The timestamp is an integer value representing the UNIX

Modified: torvm/trunk/TODO
===================================================================
--- torvm/trunk/TODO	2009-06-09 15:45:19 UTC (rev 19680)
+++ torvm/trunk/TODO	2009-06-09 16:09:43 UTC (rev 19681)
@@ -17,18 +17,10 @@
    . Add in pending changes, chapters to design document.
 
    Update upstream package support in build infrastructure
-   - Bypass OpenWRT MD5 package verification entirely with our own
-     download process like the win32 build stage.
-   ? OR(and?) Use Emdebian Crush and signature based verification
-     initial testing indicates this should work without much hassle.
-   ? OR(and?) Track upstream commits in a git repo and move to signed
-     changesets of current and tested versions.
    . Integrate autotools / autoconf support so build scripts are less
      completely kludged together.
 
    Update build automation docs and hooks
-   ? Add buildbot support into win32 ISO image so non-full builds are
-     possible easily and requisite perl parts are present.
    ? Replace build all script with component based Makefiles with
      proper dependency checking and conditional build support.