1 $Id: INSTALL,v 1.17 2004/03/01 22:16:02 robbiew Exp $
6 1> tar xzf ltp-XXXXXXXX.tar.gz
12 *NOTE: The LTP assumes the existence of the nobody, bin, and daemon users and
13 their groups. If these IDs do not exist, certain tests will fail. The users
14 and groups IDs should be the same, i.e. if user "nobody" is 99, then it's
15 group should also be "99". The names of the groups are irrelevant.
21 Beyond the "Quick Start" instructions, there are only a few other things
22 that should be done. The Linux Test Project build process uses a
23 minimalist approach. There is a lot of room for improvement and
24 contributions are welcome.
28 2. Untar the ltp tarball into a spare directory. There is not a
29 standard location for it yet. We put it in our home directory
30 while we're working on it.
32 3. Run "make" to build everything.
33 *NOTE: Some of the Makefiles (example: pan/Makefile) require the lex (or
34 flex) package to be installed.
36 4. You can run all of the tests sequentially by using the example test
37 script runalltests.sh. The script is there just to get you started.
38 See pan(1) for more information on the test driver we have provided.
39 It is simple, but it can do a lot of stuff.
41 NOTE: The diskio and network tests will NOT be run by the runalltests.sh
42 script. We chose to separate these tests because of their required setup
45 5. The disk i/o tests can be run by executing the diskio.sh script. In order
46 for these tests to successfully operate a writable high-density 3.5" floppy
47 must be in the disk drive and a CD-ROM with more than 100Mb of data must be
48 in the CD-ROM drive. The corresponding tests will fail if either disk is
51 6. The network tests are executed by running the networktests.sh script. The
52 network tests require some configuration for them to work correctly:
54 i) First, there MUST be another test machine setup to act as the server
55 to these client side tests. This machine MUST have the LTP installed
56 in the same exact location, i.e. if the client has /root/ltp, then the
57 server must have /root/ltp. This is required because certain tests
58 expect to find server files in certain locations. Make sure to compile
59 the LTP on this server machine also.
61 ii) Second, the server must be setup to allow the client to connect using
62 the "r" commands, such as rsh. This is done by simply creating/editing
63 the ".rhosts" file under /root. Place the hostname of the client
64 machine in this file to allow root to remotely connect without the use
67 iii) Next, certain services must be activated in order for certain tests to
68 execute. The following services are activated via inetd/xinetd:
75 Also, because certain RPC programs are tested, the "portmapper" daemon
76 MUST be started, as well as NFS server AND lock services.
78 iv) Finally, before running the networktests.sh script, two variables must
79 be set within the script file. The "RHOST" variable should be set to
80 the hostname of the server. The "PASSWD" variable should be set to
81 root's password on the server machine. This is necessary for tests
82 such as telnet01 and ftp01.
84 You can now successfully execute the networktests.sh script.