subrata_modak | 4045517 | 2009-01-05 08:35:21 +0000 | [diff] [blame] | 1 | $Id: INSTALL,v 1.20 2009/01/05 08:35:21 subrata_modak Exp $ |
subrata_modak | aba85b9 | 2008-12-11 10:30:33 +0000 | [diff] [blame] | 2 | |
| 3 | About configuration |
| 4 | ------------------- |
| 5 | If you want to use auto configuration, be sure autoconf-2.61 is installed. |
| 6 | (Autoconf sources can be downloaded from: |
| 7 | ftp://ftp.gnu.org/gnu/autoconf/autoconf-2.61.tar.gz |
| 8 | ftp://ftp.gnu.org/gnu/autoconf/autoconf-2.61.tar.bz2). |
| 9 | Then run: |
| 10 | $ make autoconf |
| 11 | $ ./configure |
| 12 | $ make all |
| 13 | |
subrata_modak | 4045517 | 2009-01-05 08:35:21 +0000 | [diff] [blame] | 14 | If you get a build error, please report it to ltp-list@lists.sf.net with |
| 15 | following information, |
| 16 | |
| 17 | 1. the error output of build tools(make, gcc, etc...) |
| 18 | 2. the output of ./configure |
| 19 | 3. include/config.h |
| 20 | 4. config.mk |
| 21 | 5. config.log |
| 22 | |
| 23 | |
subrata_modak | aba85b9 | 2008-12-11 10:30:33 +0000 | [diff] [blame] | 24 | If you want to use default configuration, autoconf is not needed. Just run: |
| 25 | $ touch include/config.h.default |
| 26 | $ make config.h |
| 27 | $ make all |
| 28 | |
| 29 | If make all is failed even if you use the auto configuration, please, report it to |
| 30 | ltp developers with config.log, generated by running the configure script. |
alaffin | e15dd68 | 2000-05-08 20:31:30 +0000 | [diff] [blame] | 31 | |
nstraz | 0312c25 | 2000-09-26 20:59:21 +0000 | [diff] [blame] | 32 | Quick Start |
| 33 | ----------- |
whr | b973f2b | 2000-05-05 19:34:50 +0000 | [diff] [blame] | 34 | |
robbiew | 5740448 | 2001-09-19 16:11:23 +0000 | [diff] [blame] | 35 | 1> tar xzf ltp-XXXXXXXX.tar.gz |
nstraz | 0312c25 | 2000-09-26 20:59:21 +0000 | [diff] [blame] | 36 | 2> cd ltp |
robbiew | 0eea352 | 2004-02-05 17:33:10 +0000 | [diff] [blame] | 37 | 3> make |
robbiew | 502f4ca | 2003-02-05 16:30:06 +0000 | [diff] [blame] | 38 | 4> make install |
| 39 | 5> ./runalltests.sh |
whr | b973f2b | 2000-05-05 19:34:50 +0000 | [diff] [blame] | 40 | |
robbiew | 0eea352 | 2004-02-05 17:33:10 +0000 | [diff] [blame] | 41 | *NOTE: The LTP assumes the existence of the nobody, bin, and daemon users and |
| 42 | their groups. If these IDs do not exist, certain tests will fail. The users |
| 43 | and groups IDs should be the same, i.e. if user "nobody" is 99, then it's |
| 44 | group should also be "99". The names of the groups are irrelevant. |
robbiew | 5be3ca5 | 2001-10-12 20:21:49 +0000 | [diff] [blame] | 45 | |
whr | b973f2b | 2000-05-05 19:34:50 +0000 | [diff] [blame] | 46 | |
nstraz | 0312c25 | 2000-09-26 20:59:21 +0000 | [diff] [blame] | 47 | Detailed Installation |
| 48 | --------------------- |
| 49 | |
| 50 | Beyond the "Quick Start" instructions, there are only a few other things |
| 51 | that should be done. The Linux Test Project build process uses a |
| 52 | minimalist approach. There is a lot of room for improvement and |
| 53 | contributions are welcome. |
| 54 | |
robbiew | b6c5fe7 | 2001-09-18 20:44:30 +0000 | [diff] [blame] | 55 | 1. Log in as root. |
| 56 | |
| 57 | 2. Untar the ltp tarball into a spare directory. There is not a |
robbiew | fc0708b | 2004-03-01 22:16:02 +0000 | [diff] [blame] | 58 | standard location for it yet. We put it in our home directory |
robbiew | 0eea352 | 2004-02-05 17:33:10 +0000 | [diff] [blame] | 59 | while we're working on it. |
nstraz | 0312c25 | 2000-09-26 20:59:21 +0000 | [diff] [blame] | 60 | |
robbiew | 0eea352 | 2004-02-05 17:33:10 +0000 | [diff] [blame] | 61 | 3. Run "make" to build everything. |
| 62 | *NOTE: Some of the Makefiles (example: pan/Makefile) require the lex (or |
| 63 | flex) package to be installed. |
nstraz | 0312c25 | 2000-09-26 20:59:21 +0000 | [diff] [blame] | 64 | |
nstraz | 0312c25 | 2000-09-26 20:59:21 +0000 | [diff] [blame] | 65 | 4. You can run all of the tests sequentially by using the example test |
| 66 | script runalltests.sh. The script is there just to get you started. |
| 67 | See pan(1) for more information on the test driver we have provided. |
robbiew | 0eea352 | 2004-02-05 17:33:10 +0000 | [diff] [blame] | 68 | It is simple, but it can do a lot of stuff. |
robbiew | b6c5fe7 | 2001-09-18 20:44:30 +0000 | [diff] [blame] | 69 | |
robbiew | 0eea352 | 2004-02-05 17:33:10 +0000 | [diff] [blame] | 70 | NOTE: The diskio and network tests will NOT be run by the runalltests.sh |
| 71 | script. We chose to separate these tests because of their required setup |
| 72 | overhead. |
nstraz | 0312c25 | 2000-09-26 20:59:21 +0000 | [diff] [blame] | 73 | |
robbiew | 0eea352 | 2004-02-05 17:33:10 +0000 | [diff] [blame] | 74 | 5. The disk i/o tests can be run by executing the diskio.sh script. In order |
robbiew | ba42204 | 2001-09-19 15:25:43 +0000 | [diff] [blame] | 75 | for these tests to successfully operate a writable high-density 3.5" floppy |
| 76 | must be in the disk drive and a CD-ROM with more than 100Mb of data must be |
| 77 | in the CD-ROM drive. The corresponding tests will fail if either disk is |
| 78 | missing. |
nstraz | 0312c25 | 2000-09-26 20:59:21 +0000 | [diff] [blame] | 79 | |
robbiew | ba42204 | 2001-09-19 15:25:43 +0000 | [diff] [blame] | 80 | 6. The network tests are executed by running the networktests.sh script. The |
| 81 | network tests require some configuration for them to work correctly: |
| 82 | |
| 83 | i) First, there MUST be another test machine setup to act as the server |
| 84 | to these client side tests. This machine MUST have the LTP installed |
| 85 | in the same exact location, i.e. if the client has /root/ltp, then the |
| 86 | server must have /root/ltp. This is required because certain tests |
| 87 | expect to find server files in certain locations. Make sure to compile |
| 88 | the LTP on this server machine also. |
| 89 | |
robbiew | 0eea352 | 2004-02-05 17:33:10 +0000 | [diff] [blame] | 90 | ii) Second, the server must be setup to allow the client to connect using |
subrata_modak | 08978d2 | 2008-12-18 04:58:57 +0000 | [diff] [blame] | 91 | the "r" commands, such as rsh. This is done by simply creating/editing |
| 92 | the ".rhosts" file under /root. Place the hostname of the client |
| 93 | machine in this file to allow root to remotely connect without the use |
| 94 | of a password. If server has the PAM system security tool, you need |
| 95 | to add the following lines to /etc/securetty: |
| 96 | rlogin |
| 97 | rsh |
| 98 | rexec |
| 99 | pts/0 |
| 100 | pts/1 |
| 101 | : |
| 102 | pts/9 |
robbiew | ba42204 | 2001-09-19 15:25:43 +0000 | [diff] [blame] | 103 | |
robbiew | 0eea352 | 2004-02-05 17:33:10 +0000 | [diff] [blame] | 104 | iii) Next, certain services must be activated in order for certain tests to |
robbiew | ba42204 | 2001-09-19 15:25:43 +0000 | [diff] [blame] | 105 | execute. The following services are activated via inetd/xinetd: |
| 106 | rlogind |
| 107 | ftpd |
| 108 | telnetd |
| 109 | echo (stream) |
| 110 | fingerd |
| 111 | rshd |
subrata_modak | 08978d2 | 2008-12-18 04:58:57 +0000 | [diff] [blame] | 112 | Also, because certain RPC programs are tested, the "portmapper" daemon |
| 113 | MUST be started, as well as NFS server AND lock services. |
robbiew | ba42204 | 2001-09-19 15:25:43 +0000 | [diff] [blame] | 114 | |
robbiew | 0eea352 | 2004-02-05 17:33:10 +0000 | [diff] [blame] | 115 | iv) Finally, before running the networktests.sh script, two variables must |
subrata_modak | 08978d2 | 2008-12-18 04:58:57 +0000 | [diff] [blame] | 116 | be set within the script file. The "RHOST" variable should be set to |
| 117 | the hostname of the server. The "PASSWD" variable should be set to |
| 118 | root's password on the server machine. This is necessary for tests |
| 119 | such as telnet01 and ftp01. |
robbiew | ba42204 | 2001-09-19 15:25:43 +0000 | [diff] [blame] | 120 | |
| 121 | You can now successfully execute the networktests.sh script. |
subrata_modak | 08978d2 | 2008-12-18 04:58:57 +0000 | [diff] [blame] | 122 | When you would like to run the whole network tests, specify -w option: |
| 123 | # ./networktests.sh -w |
| 124 | |
| 125 | When you would like to run the same tests which networktests.sh ran till |
| 126 | 2008, specify no option or -d option: |
| 127 | # ./networktests.sh |
| 128 | |
| 129 | You can run the test category which you are interested in, -h option shows |
| 130 | the list of the test category: |
| 131 | # ./netwoktests.sh -h |