ckubwr.txt

KERMIT工具 这在办公室下载不了,很多人都没有载不到.

                       C-Kermit 8.0 Unix Hints and Tips

     Frank da Cruz
     [1]The Kermit Project, [2]Columbia University

   As of: C-Kermit 8.0.211 10 April 2004
   This page last updated: Fri Apr 16 16:13:14 2004 (New York USA Time)

     IF YOU ARE READING A PLAIN-TEXT version of this document, note it
     is a plain-text dump of a Web page. You can visit the original (and
     possibly more up-to-date) Web page here:

  [3]http://www.columbia.edu/kermit/ckubwr.html

     Since the material in this file has been accumulating since 1985,
     some (much) of it might be dated. [4]Feedback from experts on
     particular OS's and platforms is always welcome. 

   [ [5]C-Kermit ] [ [6]Installation Instructions ] [ [7]TUTORIAL ]
    ________________________________________________________________________

  CONTENTS

    1. [8]INTRODUCTION
    2. [9]PREBUILT C-KERMIT BINARIES
    3. [10]PLATFORM-SPECIFIC NOTES
    4. [11]GENERAL UNIX-SPECIFIC LIMITATIONS AND BUGS
    5. [12]INITIALIZATION AND COMMAND FILES
    6. [13]COMMUNICATION SPEED SELECTION
    7. [14]COMMUNICATIONS AND DIALING
    8. [15]HARDWARE FLOW CONTROL
    9. [16]TERMINAL CONNECTION AND KEY MAPPING
   10. [17]FILE TRANSFER
   11. [18]EXTERNAL FILE TRANSFER PROTOCOLS
   12. [19]SECURITY
   13. [20]MISCELLANEOUS USER REPORTS
   14. [21]THIRD-PARTY DRIVERS

   Quick Links:   [ [22]Linux ] [ [23]*BSD ] [[24]Mac OS X] [ [25]AIX ] [
   [26]HP-UX ] [ [27]Solaris ] [ [28]SCO ] [ [29]DEC/Compaq ]
    ________________________________________________________________________

  1. INTRODUCTION

   [ [30]Top ] [ [31]Contents ] [ [32]Next ]

   SECTION CONTENTS

  1.1. [33]Documentation
  1.2. [34]Technical Support
  1.3. [35]The Year 2000
  1.4. [36]The Euro

   THIS IS WHAT USED TO BE CALLED the "beware file" for the Unix version
   of C-Kermit, previously distributed as ckubwr.txt and, before that, as
   ckuker.bwr, after the fashion of old Digital Equipment Corporation
   (DEC) software releases that came with release notes (describing what
   had changed) and a "beware file" listing known bugs, limitations,
   "non-goals", and things to watch out for. The C-Kermit beware file has
   been accumulating since 1985, and it applies to many different
   hardware platforms and operating systems, and many versions of them,
   so it is quite large. Prior to C-Kermit 8.0, it was distributed only
   in plain-text format. Now it is available as a Web document with
   links, internal cross references, and so on, to make it easier to use.

   This document applies to Unix C-Kermit in general, as well as to
   specific Unix variations like [37]Linux, [38]AIX, [39]HP-UX,
   [40]Solaris, and so on, and should be read in conjunction with the
   [41]platform-independent C-Kermit beware file, which contains similar
   information, but applying to all versions of C-Kermit (VMS, Windows,
   OS/2, AOS/VS, VOS, etc, as well as to Unix).

   There is much in this document that is (only) of historical interest.
   The navigation links should help you skip directly to the sections
   that are relevant to you. Numerous offsite Web links are supposed to
   lead to further information but, as you know, Web links go stale
   frequently and without warning. If you can supply additional,
   corrected, updated, or better Web links, please feel free to [42]let
   us know.

  1.1. Documentation

   [ [43]Top ] [ [44]Contents ] [ [45]Next ]

   C-Kermit 6.0 is documented in the book [46]Using C-Kermit, Second
   Edition, by Frank da Cruz and Christine M. Gianone, Digital Press,
   Burlington, MA, USA, ISBN 1-55558-164-1 (1997), 622 pages. This
   remains the definitive C-Kermit documentation. Until the third edition
   is published (sorry, there is no firm timeframe for this), please also
   refer to:

   [47]Supplement to Using C-Kermit, Second Edition, For C-Kermit 7.0
          Thorough documentation of features new to version 7.0.

   [48]Supplement to Using C-Kermit, Second Edition, For C-Kermit 8.0
          Thorough documentation of features new to version 8.0.

  1.2. Technical Support

   [ [49]Top ] [ [50]Contents ] [ [51]Section Contents ] [ [52]Next ] [
   [53]Previous ]

   For information on how to get technical support, please visit:

    [54]http://www.columbia.edu/kermit/support.html

  1.3. The Year 2000

   [ [55]Top ] [ [56]Contents ] [ [57]Section Contents ] [ [58]Next ] [
   [59]Previous ]

   The Unix version of C-Kermit, release 6.0 and later, is "Year 2000
   compliant", but only if the underlying operating system is too.
   Contact your Unix operating system vendor to find out which operating
   system versions, patches, hardware, and/or updates are required.
   (Quite a few old Unixes are still in operation in the new millenium,
   but with their date set 28 years in the past so at least the non-year
   parts of the calendar are correct.)

   As of C-Kermit 6.0 (6 September 1996), post-millenium file dates are
   recognized, transmitted, received, and reproduced correctly during the
   file transfer process in C-Kermit's File Attribute packets. If
   post-millenium dates are not processed correctly on the other end,
   file transfer still takes place, but the modification or creation date
   of the received file might be incorrect. The only exception would be
   if the "file collision update" feature is being used to prevent
   unnecessary transfer of files that have not changed since the last
   time a transfer took place; in this case, a file might be transferred
   unnecessarily, or it might not be transferred when it should have
   been. Correct operation of the update feature depends on both Kermit
   programs having the correct date and time.

   Of secondary importance are the time stamps in the transaction and/or
   debug logs, and the date-related script programming constructs, such
   as \v(date), \v(ndate), \v(day), \v(nday), and perhaps also the
   time-related ones, \v(time) and \v(ntime), insofar as they might be
   affected by the date. The \v(ndate) is a numeric-format date of the
   form yyyymmdd, suitable for both lexical and numeric comparison and
   sorting: e.g. 19970208 or 20011231. If the underlying operating system
   returns the correct date information, these variables will have the
   proper values. If not, then scripts that make decisions based on these
   variables might not operate correctly.

   Most date-related code is based upon the C Library asctime() string,
   which always has a four-digit year. In Unix, the one bit of code in
   C-Kermit that is an exception to this rule is several calls to
   localtime(), which returns a pointer to a tm struct, in which the year
   is presumed to be expressed as "years since 1900". The code depends on
   this assumption. Any platforms that violate it will need special
   coding. As of this writing, no such platforms are known.

   Command and script programming functions that deal with dates use
   C-Kermit specific code that always uses full years.

  1.4. The Euro

   [ [60]Top ] [ [61]Contents ] [ [62]Section Contents ] [ [63]Previous ]

   C-Kermit 7.0 and later support Unicode (ISO 10646), ISO 8859-15 Latin
   Alphabet 9, PC Code Page 858, Windows Code Pages 1250 and 1251, and
   perhaps other character sets, that encode the Euro symbol, and can
   translate among them as long as no intermediate character-set is
   involved that does not include the Euro.
    ________________________________________________________________________

  2. PREBUILT C-KERMIT BINARIES

   [ [64]Top ] [ [65]Contents ] [ [66]Next ] [ [67]Previous ]

   It is often dangerous to run a binary C-Kermit (or any other) program
   built on a different computer. Particularly if that computer had a
   different C compiler, libraries, operating system version, processor
   features, etc, and especially if the program was built with shared
   libraries, because as soon as you update the libraries on your system,
   they no longer match the ones referenced in the binary, and the binary
   might refuse to load when you run it, in which case you'll see error
   messages similar to:

  Could not load program kermit
  Member shr4.o not found or file not an archive
  Could not load library libcurses.a[shr4.o]
  Error was: No such file or directory

   (These samples are from AIX.) To avoid this problem, we try to build
   C-Kermit with statically linked libraries whenever we can, but this is
   increasingly impossible as shared libraries become the norm.

   It is often OK to run a binary built on an earlier OS version, but it
   is rarely possible (or safe) to run a binary built on a later one, for
   example to run a binary built under Solaris 8 on Solaris 2.6.
   Sometimes even the OS-or-library patch/ECO level makes a difference.

   A particularly insidious problem occurs when a binary was built on a
   version of the OS that has patches from the vendor (e.g. to
   libraries); in many cases you won't be able to run such a binary on an
   unpatched version of the same platform.

   When in doubt, build C-Kermit from the source code on the computer
   where it is to be run (if possible!). If not, ask us for a binary
   specific to your configuration. We might have one, and if we don't, we
   might be able to find somebody who will build one for you.
    ________________________________________________________________________

  3. NOTES ON SPECIFIC UNIX VERSIONS

   [ [68]Top ] [ [69]Contents ] [ [70]Next ] [ [71]Previous ]

   SECTION CONTENTS

  3.0.  [72]C-KERMIT ON PC-BASED UNIXES
  3.1.  [73]C-KERMIT AND AIX
  3.2.  [74]C-KERMIT AND HP-UX
  3.3.  [75]C-KERMIT AND LINUX
  3.4.  [76]C-KERMIT AND NEXTSTEP
  3.5.  [77]C-KERMIT AND QNX
  3.6.  [78]C-KERMIT AND SCO
  3.7.  [79]C-KERMIT AND SOLARIS
  3.8.  [80]C-KERMIT AND SUNOS
  3.9.  [81]C-KERMIT AND ULTRIX
  3.10. [82]C-KERMIT AND UNIXWARE
  3.11. [83]C-KERMIT AND APOLLO SR10
  3.12. [84]C-KERMIT AND TANDY XENIX 3.0
  3.13. [85]C-KERMIT AND OSF/1 (DIGITAL UNIX) (TRU64 UNIX)
  3.14. [86]C-KERMIT AND SGI IRIX
  3.15. [87]C-KERMIT AND THE BEBOX
  3.16. [88]C-KERMIT AND DG/UX
  3.17. [89]C-KERMIT AND SEQUENT DYNIX
  3.18. [90]C-KERMIT AND {FREE,OPEN,NET}BSD
  3.19. [91]C-KERMIT AND MAC OS X
  3.20. [92]C-KERMIT AND COHERENT

   The following sections apply to specific Unix versions. Most of them
   contain references to FAQs (Frequently Asked Questions), but these
   tend to be ephemeral. For possibly more current information see:

  [93]http://www.faqs.org
  [94]http://aplawrence.com/Unixart/newtounix.html

   One thread that runs through many of them, and implicitly perhaps
   through all, concerns the problems that occur when trying to dial out
   on a serial device that is (also) enabled for dialing in. The
   "solutions" to this problem are many, varied, diverse, and usually
   gross, involving configuring the device for bidirectional use. This is
   done in a highly OS-dependent and often obscure manner, and the
   effects (good or evil) are also highly dependent on the particular OS
   (and getty variety, etc). Many examples are given in the
   [95]OS-specific sections below.

   An important point to keep in mind is that C-Kermit is a
   cross-platform, portable software program. It was not designed
   specifically and only for your particular Unix version, or for that
   matter, for Unix in particular at all. It also runs on VMS, AOS/VS,
   VOS, and other non-Unix platforms. All the Unix versions of C-Kermit
   share common i/o modules, with compile-time #ifdef constructions used
   to account for the differences among the many Unix products and
   releases. If you think that C-Kermit is behaving badly or missing
   something on your particular Unix version, you might be right -- we
   can't claim to be expert in hundreds of different OS / version /
   hardware / library combinations. If you're a programmer, take a look
   at the source code and [96]send us your suggested fixes or changes. Or
   else just [97]send us a report about what seems to be wrong and we'll
   see what we can do.
    ________________________________________________________________________

  3.0. C-KERMIT ON PC-BASED UNIXES

   [ [98]Top ] [ [99]Contents ] [ [100]Section Contents ] [ [101]Next ]

   Also see: [102]http://www.pcunix.com/.

   SECTION CONTENTS

  3.0.1. [103]Interrupt Conflicts
  3.0.2. [104]Windows-Specific Hardware
  3.0.3. [105]Modems
  3.0.4. [106]Character Sets
  3.0.5. [107]Keyboard, Screen, and Mouse Access
  3.0.6. [108]Laptops