Browse files

Kali Scheme from the kali-0.52.2.tar.gz release tarball

  • Loading branch information...
0 parents commit 79bf76b4964729b63fce99c4d2149b32cb067ac0 @tonyg committed Apr 11, 2012
Showing 492 changed files with 102,072 additions and 0 deletions.
@@ -0,0 +1,60 @@
+Copyright (c) 1993, 1994 by Richard Kelsey and Jonathan Rees.
+Copyright (c) 1996 by NEC Research Institute, Inc.
+Use of this software for non-commercial academic purposes is
+permitted provided that the above copyright notice appears
+in the software itself and in the accompanying documentation
+and this permission notice appears in the documentation.
+Use of this software for commerical purposes is also
+permitted, but only if, in addition to the conditions
+required for non-commerical users, written notification of
+such use is provided by the commerical user to NEC Research
+Institute, Inc. (NECI) prior to the fabrication and
+distribution of the software.
+This software is experimental. NECI does not make any
+representations regarding the suitability of the software
+for any purpose and NECI will not support the software. The
+software is provided "AS IS". NECI does not make any
+warranties either express or implied with regard to the
+NECI also disclaims any warranty that the software is free
+of infringement of any intellectual property rights of
+others. No other license express or implied is hereby
+provided. Users of this software for commercial purposes
+agree to indemnify and hold harmless NECI from any claims
+whatsoever arising from the commercial use or distribution
+of the software, including claims and/or actions arising
+from infringement of intellectual property rights.
+NECI shall not be liable for any damages, including general,
+special, incidental or consequential, arising out of the use
+or inability to use the software.
+The name of NEC Research Institute, Inc. shall not be used in
+advertising or publicity related to the distribution of the
+software, without the prior written consent of NECI.
+Distributing Autoconf Output
+[excerpt from autoconf documentation]
+ The configuration scripts that Autoconf produces are covered by the
+GNU General Public License. This is because they consist almost
+entirely of parts of Autoconf itself, rearranged somewhat, and Autoconf
+is distributed under the terms of the GPL. As applied to Autoconf, the
+GPL just means that you need to distribute `' along with
+ Programs that use Autoconf scripts to configure themselves do not
+automatically come under the GPL. Distributing an Autoconf
+configuration script as part of a program is considered to be *mere
+aggregation* of that work with the Autoconf script. Such programs are
+not derivative works based on Autoconf; only their configuration scripts
+are. We still encourage software authors to distribute their work under
+terms like those of the GPL, but doing so is not required to use
@@ -0,0 +1,120 @@
+ This is a generic INSTALL file for utilities distributions.
+If this package does not come with, e.g., installable documentation or
+data files, please ignore the references to them below.
+ [For information specific to Scheme 48, see doc/install.txt.]
+ The `configure' shell script attempts to guess correct values for
+various system-dependent variables used during compilation, and
+creates the Makefile(s) (one in each subdirectory of the source
+directory). In some packages it creates a C header file containing
+system-dependent definitions. It also creates a file `config.status'
+that you can run in the future to recreate the current configuration.
+To compile this package:
+1. Configure the package for your system.
+ Normally, you just `cd' to the directory containing the package's
+source code and type `./configure'. If you're using `csh' on an old
+version of System V, you might need to type `sh configure' instead to
+prevent `csh' from trying to execute `configure' itself.
+ Running `configure' takes a minute or two. While it is running, it
+prints some messages that tell what it is doing. If you don't want to
+see the messages, run `configure' with its standard output redirected
+to `/dev/null'; for example, `./configure >/dev/null'.
+ To compile the package in a different directory from the one
+containing the source code, you must use a version of `make' that
+supports the `VPATH' variable, such as GNU `make'. `cd' to the
+directory where you want the object files and executables to go and run
+the `configure' script. `configure' automatically checks for the
+source code in the directory that `configure' is in and in `..'. If
+for some reason `configure' is not in the source code directory that
+you are configuring, then it will report that it can't find the source
+code. In that case, run `configure' with the option `--srcdir=DIR',
+where DIR is the directory that contains the source code.
+ By default, `make install' will install the package's files in
+`/usr/local/bin', `/usr/local/man', etc. You can specify an
+installation prefix other than `/usr/local' by giving `configure' the
+option `--prefix=PATH'. Alternately, you can do so by consistently
+giving a value for the `prefix' variable when you run `make', e.g.,
+ make prefix=/usr/gnu
+ make prefix=/usr/gnu install
+ You can specify separate installation prefixes for
+architecture-specific files and architecture-independent files. If you
+give `configure' the option `--exec-prefix=PATH' or set the `make'
+variable `exec_prefix' to PATH, the package will use PATH as the prefix
+for installing programs and libraries. Data files and documentation
+will still use the regular prefix. Normally, all files are installed
+using the same prefix.
+ Some packages pay attention to `--with-PACKAGE' options to
+`configure', where PACKAGE is something like `gnu-as' or `x' (for the X
+Window System). The README should mention any `--with-' options that
+the package recognizes.
+ `configure' ignores any other arguments that you give it.
+ On systems that require unusual options for compilation or linking
+that the package's `configure' script does not know about, you can give
+`configure' initial values for variables by setting them in the
+environment. In Bourne-compatible shells, you can do that on the
+command line like this:
+ CC='gcc -traditional' LIBS=-lposix ./configure
+ Here are the `make' variables that you might want to override with
+environment variables when running `configure'.
+ For these variables, any value given in the environment overrides the
+value that `configure' would choose:
+ - Variable: CC
+ C compiler program. The default is `cc'.
+ - Variable: INSTALL
+ Program to use to install files. The default is `install' if you
+ have it, `cp' otherwise.
+ For these variables, any value given in the environment is added to
+the value that `configure' chooses:
+ - Variable: DEFS
+ Configuration options, in the form `-Dfoo -Dbar...'. Do not use
+ this variable in packages that create a configuration header file.
+ - Variable: LIBS
+ Libraries to link with, in the form `-lfoo -lbar...'.
+ If you need to do unusual things to compile the package, we encourage
+you to figure out how `configure' could check whether to do them, and
+mail diffs or instructions to the address given in the README so we
+can include them in the next release.
+2. Type `make' to compile the package. If you want, you can override
+the `make' variables CFLAGS and LDFLAGS like this:
+ make CFLAGS=-O2 LDFLAGS=-s
+3. If the package comes with self-tests and you want to run them,
+type `make check'. If you're not sure whether there are any, try it;
+if `make' responds with something like
+ make: *** No way to make target `check'. Stop.
+then the package does not come with self-tests.
+4. Type `make install' to install programs, data files, and
+5. You can remove the program binaries and object files from the
+source directory by typing `make clean'. To also remove the
+Makefile(s), the header file containing system-dependent definitions
+(if the package uses one), and `config.status' (all the files that
+`configure' created), type `make distclean'.
+ The file `' is used to create `configure' by a program
+called `autoconf'. You only need it if you want to regenerate
+`configure' using a newer version of `autoconf'.
@@ -0,0 +1,11 @@
+To make kali, follow the instructions in INSTALL. It has to be
+installed some where in your PATH. (Before you do a
+ make install
+you can try it out by running the `go' file in the source directory.)
+Documentation on using Kali can be found in doc/kali.{ps|html}.
+If you have problems building or using Kali, please send mail to
+and we'll see if we can be of any help.
Oops, something went wrong.

0 comments on commit 79bf76b

Please sign in to comment.