ETFTP - Enhanced Trivial File Transfer Protocol. Adaptive transmission protocol for radio based data transmission. Copyright (C) 1997, 1998 Defence Research Establishment, Dept. of Comm. Systems, FOA 72, Sweden. Currently maintained by Christian Jönsson FOA 72 <chj@lin.foa.se> and Torbjörn Frostemark FOA 72 <torfr@lin.foa.se>. This file is part of ETFTP version 1.1.3. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; see the file GPL. If not, write to the Free Software Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. ETFTP version 1.1.3 was implemented in ANSI C for UNIX using Linux RedHat 5.1. This implementation could work on other UNIX systems. Basic Installation ================== These are generic installation instructions. The `configure' shell script attempts to guess correct values for various system-dependent variables used during compilation. It uses those values to create a `Makefile' in each directory of the package. It may also create one or more `.h' files containing system-dependent definitions. Finally, it creates a shell script `config.status' that you can run in the future to recreate the current configuration, a file `config.cache' that saves the results of its tests to speed up reconfiguring, and a file `config.log' containing compiler output (useful mainly for debugging `configure'). If you need to do unusual things to compile the package, please try to figure out how `configure' could check whether to do them, and mail diffs or instructions to the address given in the `README' so they can be considered for the next release. If at some point `config.cache' contains results you don't want to keep, you may remove or edit it. The file `configure.in' is used to create `configure' by a program called `autoconf'. You only need `configure.in' if you want to change it or regenerate `configure' using a newer version of `autoconf'. The simplest way to compile and install this package is: 1. `cd' to the directory containing the package's source code and type `./configure' to configure the package for your system. 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 awhile. While running, it prints some messages telling which features it is checking for. 2. Type `make' to compile the package including both clinet and server parts. Type `make etftp' to only compile the client part or `make etftpd' to only compile the server part. 3. Type `make install' to install both client and server programs. Type `make install-client' to install only the client program or `make install-server' to install only the server program. `make install' and `make install-server' also creates a symbolic link `in.etftpd' that points to etftpd and resides where the server daemon is located (see Installation names below). The symbolic link used by the inetd (see Running ETFTP below). 4. You can remove the program binaries and object files from the source directory by typing `make clean'. To also remove the files that `configure' created (so you can compile the package for a different kind of computer), type `make distclean'. Installation Names ================== By default, `make install' will install the package's client file in `/usr/local/bin' and the server files in `/usr/local/sbin'. You can specify an installation prefix other than `/usr/local' by giving `configure' the option `--prefix=PATH'. You can specify separate installation prefixes for architecture-specific files and architecture-independent files. If you give `configure' the option `--exec-prefix=PATH', the package will use PATH as the prefix for installing programs and libraries. Documentation and other data files will still use the regular prefix. Uninstall the package ===================== To unistall the package, simply type `make uninstall' and the binary files will be removed. Source files will still remain intact. Make a distribution =================== To make a distribution of the package, type `make dist' for collecting source and install files together in a compressed tar file. Freely distribute this package under GNU GPL.