Return to ckc4c.ann CVS log

Up to [CSRG BSD Unix] / 43BSDReno / contrib / kermit

Annotation of 43BSDReno/contrib/kermit/ckc4c.ann, revision 1.1

1.1     ! root        1: 30-May-85 19:29:36-EDT,5278;000000000000
        !             2: Mail-From: SY.FDC created at 30-May-85 19:29:10
        !             3: Date: Thu 30 May 85 19:29:10-EDT
        !             4: From: Frank da Cruz <[email protected]>
        !             5: Subject: Info-Kermit Digest V2 #32
        !             6: To: [email protected]
        !             7: Reply-To: Info-Kermit@CU20B
        !             8: Queries-To: Info-Kermit-Request@CU20B
        !             9: 
        !            10: Info-Kermit Digest         Thu, 30 May 1985       Volume 2 : Number 32
        !            11: 
        !            12:          C-Kermit Version 4C for Unix, VMS, and the Macintosh
        !            13: 
        !            14: ----------------------------------------------------------------------
        !            15: 
        !            16: This is to announce version 4C of C-Kermit for Unix, the Apple Macintosh,
        !            17: and VAX/VMS.  C-Kermit is a version of Kermit written modularly in C,
        !            18: implementing the entire Kermit file transfer protocol (except for attribute
        !            19: packets), designed for modularity and transportability.
        !            20: 
        !            21: This version of Kermit has been in "field test" for about a month, and
        !            22: is being released at this time because most of the major goals for it have
        !            23: been met, namely:
        !            24: 
        !            25: . Most known bugs in release 4.2 fixed
        !            26: . Support for new systems added and tested
        !            27: . A few new functions incorporated
        !            28: 
        !            29: At this point, C-Kermit should be considered a fairly stable base upon which
        !            30: to add support for new systems -- the interface between the system-dependent
        !            31: and portable modules seems to have settled down -- and to add new features.
        !            32: 
        !            33: A few highlights:
        !            34: 
        !            35: Systems Supported:
        !            36:   . Berkeley Unix 4.1 and 4.2 (but not yet 2.9)
        !            37:   . AT&T Unix System III and derivatives (Xenix/286, PC/IX, etc)
        !            38:   . AT&T Unix System V and derivatives
        !            39:   . Bell Unix Version 7 
        !            40:   . DEC Pro-350 with Venix Version 1
        !            41:   . NCR Tower 1632, OS 1.02
        !            42:   . VAX/VMS
        !            43:   . Apple Macintosh
        !            44: 
        !            45: New features since version 4.2, common to all implementations:
        !            46:   . Many features redesigned to promote portability.
        !            47:   . Compile-time options to eliminate debugging and logging code to reduce
        !            48:     size and boost performance.
        !            49:   . Packet parameters separately settable for inbound & outbound packets.
        !            50:   . Protocol operation improved here & there, many bugs fixed.
        !            51: 
        !            52: New features for Unix implementation (and VMS):
        !            53:   . Command line continuation
        !            54:   . Support for additional modem-dialers
        !            55:   . Improved performance for Pro/Venix
        !            56:   . Better (but still not perfect) determination of local vs remote mode
        !            57:     in 'set line'
        !            58:   . User's preferred shell is used for "!" commands, rather than always sh.
        !            59: (A complete list of Unix/VMS updates is in CKUKER.UPD.)
        !            60: 
        !            61: New Features (since 0.7) for Macintosh:
        !            62:   . A key redefinition package is now provided.
        !            63:   . I/O errors, such as disk full or write protected, now handled better.
        !            64:   . Separate boxes for inbound & outbound packet parameters in protocol
        !            65:     settings dialog.
        !            66: (A complete list of Macintosh updates is in CKMKER.UPD.)
        !            67: 
        !            68: The Macintosh implementation is built using the Stanford University Medical
        !            69: Center's SUMACC cross development system, which runs on VAX computers under
        !            70: Unix (or VMS with Eunice).  MacKermit fits on a standard 128K Mac, but just
        !            71: barely.  The key configurator is a separate program, because this additional
        !            72: functionality added to Kermit itself would not fit into a 128K Mac.  The memory
        !            73: restriction is a problem only because the SUMACC system cannot produce
        !            74: swappable segments.  If someone wants to take the trouble to translate the
        !            75: Macintosh-specific modules to one of the native Macintosh C development systems
        !            76: that supports segment loading, then additional functionality can be added
        !            77: without worrying about exceeding memory.  (If you want to volunteer to do this,
        !            78: please contact us first!)
        !            79: 
        !            80: The VAX/VMS implementation is more an exercise in portability than a real
        !            81: Kermit implementation.  It mostly works, but does not possess the intimate
        !            82: knowledge of the VMS environment that the Stevens Institute of Technology
        !            83: Bliss language implementation has.  Still, it may be useful to sites that
        !            84: do not have a Bliss compiler but do have the VAX-11 C compiler.
        !            85: 
        !            86: Documentation includes a Unix Kermit manual (CKUKER.DOC, Scribe source
        !            87: CKUKER.MSS), a Macintosh Kermit manual (CKMKER.DOC,.MSS), various help files
        !            88: (CK*.HLP), program update histories (CK*.UPD), and "beware" files (CK*.BWR).
        !            89: The Unix and Macintosh manuals are new chapters for the Kermit User Guide,
        !            90: but the Guide itself has not yet been reissued to include these chapters;
        !            91: a new revision of the manual will appear after MS-DOS Kermit 2.28 is announced.
        !            92: 
        !            93: The files are in KER:CK*.*, available from host CU20B via anonymous FTP
        !            94: on the Internet.  Within a few days, they will also be available from BITnet
        !            95: via KERMSRV at CUVMA.  In addition, Macintosh Kermit diskettes will be sent
        !            96: out to selected sites (Apple University Consortium schools and a few others;
        !            97: our capacity to reproduce diskettes is limited, so we can't do mass
        !            98: mailings).  And of course, the new files will be included henceforth on our
        !            99: Kermit distribution tapes.
        !           100: 
        !           101: The files that had been in <CKERMIT> for testing purposes have been removed.
        !           102: Thanks to all the folks on the network who participated in the test and helped
        !           103: to work out the bugs, particularly Dave Tweten (AMES-NAS), Marco Papa (USC),
        !           104: Dan Schullman (DEC), Lawrence Afrin (Clemson U), and many others too numerous
        !           105: to mention.
        !           106: 
        !           107: Please report any problems to Info-Kermit@CU20B.
        !           108: 
        !           109: ------------------------------
        !           110: 
        !           111: End of Info-Kermit Digest
        !           112: *************************
        !           113: -------

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.