for you by putting ckermit.ini in the same directory as the Kermit       binary, adding the appropriate Kerbang line to the top, and giving       it execute permission).   In fact, you can put any number of kerbang scripts in your PATH to   start up C-Kermit in different ways, to have it adopt certain   settings, make particular connections, execute complicated scripts,   whatever you want.  5.2. Text Files   These are entirely optional. Many of them are to be found at the   Kermit website in HTML form (i.e. as Web pages with clickable links,   etc), and very likely also more up to date. Plain-text files that   correspond to Web pages were simply "dumped" by Lynx from the website   to plain ASCII text. The format is whatever Lynx uses for this   purpose. If you wish, you can install them on your computer as   described in the [159]next section.   [160]COPYING.TXT          Copyright notice, permissions, and disclaimer.   [161]ckermit.ini          The standard initialization file, intended more for reference          (in most cases) than actual use; see [162]Section 5.1.   [163]ckermod.ini          A sample customization file.   [164]ckermit70.txt          Supplement to [165]Using C-Kermit for version 7.0. Available on          the Kermit website as:          [166]http://www.columbia.edu/kermit/ckermit70.html   [167]ckermit80.txt          Supplement to [168]Using C-Kermit for version 8.0. Available on          the Kermit website as:          [169]http://www.columbia.edu/kermit/ckermit80.html   [170]ckcbwr.txt          The general C-Kermit hints and tips ("beware") file. Available          on the Kermit website as:          [171]http://www.columbia.edu/kermit/ckcbwr.html   [172]ckubwr.txt          The Unix-specific C-Kermit hints and tips file. Available on          the Kermit website as:          [173]http://www.columbia.edu/kermit/ckubwr.html   [174]ckuins.txt          Unix C-Kermit Installation Instructions (this file). Available          on the Kermit website as:          [175]http://www.columbia.edu/kermit/ckuins.html   [176]ckccfg.txt          C-Kermit compile-time configuration options. Available on the          Kermit website as:          [177]http://www.columbia.edu/kermit/ckccfg.html   [178]ckcplm.txt          The C-Kermit program logic manual. Available on the Kermit          website as:          [179]http://www.columbia.edu/kermit/ckcplm.html   [180]ca_certs.pem          Certificate Authority certificates for secure connections (see          [181]Section 16).  5.3. Installing the Kermit Files   There is an "install" target in the [182]makefile that you can use if   you wish. However, since every site has its own layout and   requirements, it is often better to install the Kermit files by hand.   You don't have to use the makefile install target to install C-Kermit.   This is especially true since not all sites build C-Kermit from   source, and therefore might not even have the makefile. But you should   read this section in any case.     If your computer already has an older version of C-Kermit     installed, you should rename it (e.g. to "kermit6" or "kermit7") so     in case you have any trouble with the new version, the old one is     still available.   In most cases, you need to be root to install C-Kermit, if only to   gain write access to directories in which the binary and manual page   are to be copied. The C-Kermit binary should be installed in a   directory that is in the users' PATH, but that is not likely to be   overwritten when you install a new version of the operating system. A   good candidate would be the /usr/local/bin/ directory, but the   specific choice is site dependent. Example (assuming the appropriate   Kermit binary is stored in your current directory as "wermit", e.g.   because you just built it from source and that's the name the makefile   gave it):mv wermit /usr/local/bin/kermitchmod 755 /usr/local/bin/kermit   or (only after you finish reading this section!) simply:make install   IMPORTANT: IF C-KERMIT IS TO BE USED FOR DIALING OUT, you must also do   something to give it access to the dialout devices and lockfile   directories. The 'install' target does not attempt to set Kermit's   owner, group, and permissions to allow dialing out. This requires   privileges, open eyes, and human decision-making. Please read   [183]Sections 10 and [184]11 below, make the necessary decisions, and   then implement them by hand as described in those sections.   You should also install the man page, which is called ckuker.nr, in   the man page directory for local commands, such as /usr/man/man1/,   renamed appropriately, e.g. to kermit.1. This is also taken care of by   "make install".   Optionally, the text files listed in the [185]previous section can be   placed in a publicly readable directory. Suggested directory names   are:/usr/local/doc/kermit//usr/local/lib/kermit//usr/share/lib/kermit//opt/kermit/doc/   (or any of these without the "/kermit"). Upon startup, C-Kermit checks   the following environment variables whose purpose is to specify the   directory where the C-Kermit text files are, in the following order:K_INFO_DIRECTORYK_INFO_DIR   If either of these is defined, C-Kermit checks for the existence of   the ckubwr.txt file (Unix C-Kermit Hints and Tips). If not found, it   checks the directories listed above (both with and without the   "/kermit") plus several others to see if they contain the ckubwr.txt   file. If found, various C-Kermit messages can refer the user to this   directory.   Finally, if you want to put the source code files somewhere for people   to look at, you can do that too.  5.4. The Makefile Install Target   The makefile "install" target does almost everything for you if you   give it the information it needs by setting the variables described   below. You can use this target if:     * You downloaded the [186]complete C-Kermit archive and built       C-Kermit from source; or:     * You downloaded an [187]individual C-Kermit binary and the       [188]C-Kermit text-file archive, and your computer has a "make"       command.   Here are the parameters you need to know:   BINARY          Name of the binary you want to install as "kermit". Default:          "wermit".   prefix          (lower case) If you define this variable, its value is          prepended to all the following xxxDIR variables (8.0.211 and          later).   DESTDIR          If you want to install the Kermit files in a directory          structure like /opt/kermit/bin/, /opt/kermit/doc/,          /opt/kermit/src/, then define DESTIR as the root of this          structure; for example, /opt/kermit. The DESTDIR string should          not end with a slash. By default, DESTDIR is not defined. If it          is defined, but the directory does not exist, the makefile          attempts to create it, which might require you to be root. Even          so, this can fail if any segments in the path except the last          one do not already exist. WARNING: If the makefile creates any          directories, it gives them a mode of 755, and the default owner          and group. Modify these by hand if necessary.   BINDIR          Directory in which to install the Kermit binary (and the          standard C-Kermit initialization file, if it is found, as a          Kerbang script). If DESTDIR is defined, BINDIR must start with          a slash. BINDIR must not end with a slash. If DESTDIR is          defined, BINDIR is a subdirectory of DESTDIR. If BINDIR does          not exist, the makefile attempts to create it as with DESTDIR.          Default: /usr/local/bin.   MANDIR          Directory in which to install the C-Kermit manual page as          "kermit" followed by the manual-chapter extension (next item).          Default: /usr/man/man1. If MANDIR is defined, the directory          must already exist.   MANEXT          Extension for the manual page. Default: 1 (digit one).   SRCDIR          Directory in which to install the C-Kermit source code. If          DESTDIR is defined, this is a subdirectory of DESTDIR. Default:          None.   CERTDIR          For secure builds only: Directory in which to install the          ca_certs.pem file. This must be the verification directory used          by programs that use the SSL libraries at your site. Default:          none. Possibilities include: /usr/local/ssl, /opt/ssl,          /usr/lib/ssl, . . .     If CERTDIR is defined, the directory          must already exist.   INFODIR          Directory in which to install the C-Kermit text files. If          DESTDIR is defined, this is a subdirectory of DESTDIR. Default:          None. If INFODIR is defined but does not exist, the makefile          attempts to create it, as with DESTDIR.   Examples:   make install          Installs "wermit" as /usr/local/bin/kermit with permissions          755, the default owner and group, and no special privileges.          The manual page is installed as /usr/man/man1/kermit.1. Text          files are not copied anywhere, nor are the sources.   make MANDIR= install          Just like "make install" but does not attempt to install the          manual page.   make DESTDIR=/opt/kermit BINDIR=/bin SRCDIR=/src INFODIR=/doc install          Installs the Kermit binary "wermit" as /opt/kermit/bin/kermit,          puts the source code in /opt/kermit/src, and puts the text          files in /opt/kermit/doc, creating the directories if they          don't already exist, and puts the man page in the default          location.   make BINDIR=/usr/local/bin CERTDIR=/usr/local/ssl install          Installs the Kerberized Kermit binary "wermit" as          /usr/local/bin/kermit, puts the CA Certificates file in          /usr/local/ssl/, and the man page in the normal place.   For definitive information, see the makefile. The following is   excerpted from the 8.0.211 makefile:# The following symbols are used to specify library and header file locations# Redefine them to the values used on your system by:# . editing this file# . defining the values on the command line# . defining the values in the environment and use the -e option#prefix  = /usr/localsrproot = $(prefix)sslroot = $(prefix)manroot = $(prefix)K4LIB=-L/usr/kerberos/libK4INC=-I/usr/kerberos/includeK5LIB=-L/usr/kerberos/libK5INC=-I/usr/kerberos/includeSRPLIB=-L$(srproot)/libSRPINC=-I$(srproot)/includeSSLLIB=-L$(sslroot)/ssl/libSSLINC=-I$(sslroot)/ssl/include...WERMIT = makewhatBINARY = wermitDESTDIR =BINDIR = $(prefix)/binMANDIR = $(manroot)/man/man1MANEXT = 1SRCDIR =INFODIR =CERTDIR =  __________________________________________________________________________6. INSTALLING UNIX C-KERMIT FROM DOS-FORMAT DISKETTES   [ [189]Top ] [ [190]Contents ] [ [191]Next ] [ [192]Previous ]     This section is obsolete. We don't distribute C-Kermit on diskettes     any more because (a)there is no demand, and (b) it no longer fits.    If you received a DOS-format diskette containing a binary executable   C-Kermit program plus supporting text files, be sure to chmod +x the   executable before attempting to run it.   In version 5A(190) and later, all the text files on the C-Kermit   DOS-format diskettes are in Unix format: LF at the end of each line   rather than CRLF. This means that no conversions are necessary when   copying to your Unix file system, and that all the files on the   diskette, text and binary, can be copied together. The following   comments apply to the DOS-format diskettes furnished with version   5A(189) and earlier or to other DOS-format diskettes you might have   obtained from other sources.   If you have received C-Kermit on MS-DOS format diskettes (such as   those distributed by Columbia University), you should m