[Prospect-cvs] prospect README.ia64,1.10,1.11

[<ty...@us...>]

Update of /cvsroot/prospect/prospect
In directory sc8-pr-cvs1:/tmp/cvs-serv6896

Modified Files:
	README.ia64 
Log Message:
Finish up ncst descrition, out for review.


Index: README.ia64
===================================================================
RCS file: /cvsroot/prospect/prospect/README.ia64,v
retrieving revision 1.10
retrieving revision 1.11
diff -C2 -d -r1.10 -r1.11
*** README.ia64	29 Apr 2003 23:57:32 -0000	1.10
--- README.ia64	1 May 2003 20:36:27 -0000	1.11
***************
*** 67,71 ****
     The supported version of oprofile (0.5.2 and beyond) has more
     stringent requirements on automake/conf.  Make sure that autoconf
!    is at least 2.53 (normal for woody) and automake is at least 1.6.
     You may have to point to testing in order to upgrade.  Versions
     from unstable (automake-1.7 1.7.4-1 and autoconf 2.57-3) have been
--- 67,71 ----
     The supported version of oprofile (0.5.2 and beyond) has more
     stringent requirements on automake/conf.  Make sure that autoconf
!    is at least 2.13 (normal for woody) and automake is at least 1.6.
     You may have to point to testing in order to upgrade.  Versions
     from unstable (automake-1.7 1.7.4-1 and autoconf 2.57-3) have been
***************
*** 399,406 ****
          kernel: oprofile 0.5.2 nsct-patch loaded, major XXX
  
! This patch allows the oprofile module to accept two parameter at load:
  addr_sys_call_table and addr_sys_mmap2.  These are the kernel addresses
  of the system call table and the mmap2 system call respectfully as found
! in a valid System.map file listing for the running kernel.
  
  The patched module then performs three validity checks before accepting
--- 399,406 ----
          kernel: oprofile 0.5.2 nsct-patch loaded, major XXX
  
! This patch allows the oprofile module to accept two parameters at load:
  addr_sys_call_table and addr_sys_mmap2.  These are the kernel addresses
  of the system call table and the mmap2 system call respectfully as found
! in a valid System.map file listing for the currently running kernel.
  
  The patched module then performs three validity checks before accepting
***************
*** 415,423 ****
          the exported sys_close address.
  
! If the above checks pass, the passed add_sys_call_table is used as the
! system call table address for system call interception that the oprofile
! module needs to do in order to implement the simple trace that both the
! oprofile tools and prospect use to implement process creation, mapping,
! and destruction models.
  
  
--- 415,449 ----
          the exported sys_close address.
  
! If the above checks pass, the passed add_sys_call_table is used as
! the system call table address for system call interception that the
! oprofile module needs to do in order to implement the simple trace
! that both the oprofile tools and prospect use to implement process
! creation, mapping, and destruction models.
! 
! Prospect needs the System.map file for creating kernel profiles and
! normally reads that file from 3 places in the following order: /boot,
! the kernel build directory found from the symlink in /lib/modules/uname
! directory, and lastly from a command line parameter.  In fact, the
! command line parameter will override both previous places if given.
! 
! If prospect detects that the sys_call_table is not exported on the
! current kernel, then the only acceptable System.map file is the one in
! /boot for generating the required addresses for the module parameters;
! unless your real user ID is root (you are running prospect as root).
! 
! This provides a rudimentary security measure to avoid spoofed
! System.map files being used to bring the system down (prospect can
! run in root suid mode) since you need root permissions in order to
! put files in /boot.
! 
! The oprofile tools have also been patched to read the System.map file
! in /boot to get these addresses automatically.  The oprofile tools
! will only read the System.map file from /boot for the same security
! reasons, even if you normally have to be root in order to run oprofile.
! 
! The security measures described here are only rudimentary and should
! not be relied upon for system security.  You must make the final
! determination if you want to make this software available on your
! system.
  
  
***************
*** 430,437 ****
  
  Currently, an oprofile variant suitable for inclusion in the kernel
! proper has been accepted for the 2.5 Linux tree.  There are efforts
! to make that work on the ia64 port as well along with a 2.4 backport
! available for both i386 and ia64 due to some work by Graydon Hoare
! and Will Cohen.
  
  The future plans for prospect, especially in the ia64 space, is to work
--- 456,462 ----
  
  Currently, an oprofile variant suitable for inclusion in the kernel
! proper has been accepted for the 2.5 Linux tree.  There are efforts to
! make that work on the ia64 port as well as a 2.4 backport available for
! both i386 and ia64 due to some work by Graydon Hoare and Will Cohen.
  
  The future plans for prospect, especially in the ia64 space, is to work