6/18/04 - jpd


- Avoid using gcc versions less than 3.2. Our development platform is 
  RH 8.0 or higher. This means avoid RH 7.x/ RH AS-2.x, SUSE 2.x .


- By default, the UNH iSCSI driver(s) are configured for a 2.4.x environment.
  You can execute "./Configure" that will attempt to select the appropriate
  Makefile for either a 2.4 or 2.6 kernel. Executing make -f Makefile
  in a sandbox seems to work, but it doesn't work in distribution because 
  on boot /etc/init.d/unh_iscsi attempts to build new drivers that much the 
  current kernel.  This is a headache that will exist for awhile.

- "make tarball " has been added for distribution purposes.

- The appropriate way to install this package is :
   1. mkdir <name> ; tar -zxf <tarball>
   2. cd <name>/unh_iscsi/src/ 
   3. ./Configure
   4. make rpm 
   5. rpm -ivh  /usr/src/redhat/RPMS/i386/unh_iscsi-1.5-0X.i386.rpm


	or if you just want a sandbox 

   1. mkdir <name> ; tar -zxf <tarball>
   2. cd <name>/unh_iscsi/src/ 
   3. ./Configure
   4. make clean ; make

   



  For an overview for porting drivers to 2.6.0 from 
  a 2.4.x thread, visit :

  http://lwn.net/Articles/driver-porting/



1/29/04 - dragonfly

- If you want to cross compile the code for 2.4.x kernel, you need to modify
  the Rules.make file with corresponding kernel directory, cross compiler you
  want to use, and extra flags for gcc.

- If you want to cross compile the code for 2.6.x kernel, you only need to
  modify the KERNEL_DIR variable in Makefile, (after you manually copy the
  Makefile-26 to Makefile). The cross compiler and flags setting will use 
  the one you defined in you kernel. You always cross compiler a kernel before
  you cross compile a module, right? :)

- WARNING !!! - For 2.6.x users. 

  If you haven't already done so , You WILL NEED THE MODULE TOOL SET
  (insmod, depmod, rmmod, etc ) version .0.9.12 or higher 
  installed to use this package.
  
  The module-init-tools kit is available from:

	http://www.kernel.org/pub/linux/kernel/people/rusty/modules/

  A quick install step for this package is :

    -  Extract the tools package.
    -   ./configure
    -   make links
    -   make install 
     
   (of course always check the most recent README file first)
 



