blob: f7d57d9507641795c14e907d677b69e37383459b [file] [log] [blame]
robbiew5be3ca52001-10-12 20:21:49 +00001$Id: INSTALL,v 1.12 2001/10/12 20:21:49 robbiew Exp $
alaffine15dd682000-05-08 20:31:30 +00002
nstraz0312c252000-09-26 20:59:21 +00003Quick Start
4-----------
whrb973f2b2000-05-05 19:34:50 +00005
robbiew57404482001-09-19 16:11:23 +000061> tar xzf ltp-XXXXXXXX.tar.gz
nstraz0312c252000-09-26 20:59:21 +000072> cd ltp
83> make
94> ./runalltests.sh
whrb973f2b2000-05-05 19:34:50 +000010
robbiew5be3ca52001-10-12 20:21:49 +000011*NOTE: The LTP assumes the existence of the nobody, bin, and daemon user/groups. If these
12do not exist, certain tests will fail.
13
whrb973f2b2000-05-05 19:34:50 +000014
nstraz0312c252000-09-26 20:59:21 +000015Detailed Installation
16---------------------
17
18Beyond the "Quick Start" instructions, there are only a few other things
19that should be done. The Linux Test Project build process uses a
20minimalist approach. There is a lot of room for improvement and
21contributions are welcome.
22
robbiewb6c5fe72001-09-18 20:44:30 +0000231. Log in as root.
24
252. Untar the ltp tarball into a spare directory. There is not a
nstraz0312c252000-09-26 20:59:21 +000026 standard location for it yet. We put it in out home directory
27 while we're working on it.
28
robbiewb6c5fe72001-09-18 20:44:30 +0000293. Run "make" to build everything.
nstraz0312c252000-09-26 20:59:21 +000030
nstraz0312c252000-09-26 20:59:21 +0000314. You can run all of the tests sequentially by using the example test
32 script runalltests.sh. The script is there just to get you started.
33 See pan(1) for more information on the test driver we have provided.
robbiewb6c5fe72001-09-18 20:44:30 +000034 It is simple, but it can do a lot of stuff.
35
robbiewba422042001-09-19 15:25:43 +000036 NOTE: The diskio and network tests will NOT be run by the runalltests.sh
37 script. We chose to seperate these tests because of there required setup
38 overhead.
nstraz0312c252000-09-26 20:59:21 +000039
robbiewba422042001-09-19 15:25:43 +0000405. The disk i/o tests can be ran by executing the diskio.sh script. Inorder
41 for these tests to successfully operate a writable high-density 3.5" floppy
42 must be in the disk drive and a CD-ROM with more than 100Mb of data must be
43 in the CD-ROM drive. The corresponding tests will fail if either disk is
44 missing.
nstraz0312c252000-09-26 20:59:21 +000045
robbiewba422042001-09-19 15:25:43 +0000466. The network tests are executed by running the networktests.sh script. The
47 network tests require some configuration for them to work correctly:
48
49 i) First, there MUST be another test machine setup to act as the server
50 to these client side tests. This machine MUST have the LTP installed
51 in the same exact location, i.e. if the client has /root/ltp, then the
52 server must have /root/ltp. This is required because certain tests
53 expect to find server files in certain locations. Make sure to compile
54 the LTP on this server machine also.
55
56 ii) Second, the server must be setup to allow the client to connect using the
57 "r" commands, such as rsh. This is done by simply creating/editing the
58 ".rhosts" file under /root. Place the hostname of the client machine
59 in this file to allow root to remotely connect without the use of a
60 password.
61
62 iii) Next, certain services must be activated in order for certain tests to
63 execute. The following services are activated via inetd/xinetd:
64 rlogind
65 ftpd
66 telnetd
67 echo (stream)
68 fingerd
69 rshd
70 Also, because certain RPC programs are tested, the "portmapper" daemon MUST
71 be started, as well as NFS server AND lock services.
72
73 iv) Finally, before running the networktests.sh script, two variables must be set
74 within the script file. The "RHOST" variable should be set to the hostname
75 of the server. The "PASSWD" variable should be set to root's password on the
76 server machine. This is neccessary for tests such as telnet01 and ftp01.
77
78 You can now successfully execute the networktests.sh script.