From f8f3c6ea3c71351899c834c2d2a821ee20f62aaf Mon Sep 17 00:00:00 2001 From: Ian Beckwith Date: Sat, 28 Jan 2012 18:51:52 +0000 Subject: [PATCH] Imported Upstream version 302 --- ck_crp.c | 6 + ckaaaa.txt | 10 +- ckc301.txt => ckc302.txt | 122 ++- ckcbwr.txt | 28 +- ckccfg.txt | 15 +- ckcftp.c | 12 +- ckcmai.c | 14 +- ckcnet.c | 12 +- ckcplm.txt | 43 +- ckermit70.txt | 261 +++--- ckermit80.txt | 112 ++- ckermit90.txt | 83 +- ckubwr.txt | 2022 +++++++++++++++++++++++----------------------- ckucmd.c | 6 + ckucon.c | 13 +- ckufio.c | 20 +- ckuins.txt | 702 ++++++++-------- ckuker.nr | 2 +- ckutio.c | 26 +- ckututor.txt | 10 +- ckuus5.c | 9 + makefile | 198 +++-- 22 files changed, 1972 insertions(+), 1754 deletions(-) rename ckc301.txt => ckc302.txt (98%) diff --git a/ck_crp.c b/ck_crp.c index ec99cdf..593d0b4 100644 --- a/ck_crp.c +++ b/ck_crp.c @@ -411,6 +411,10 @@ int des_new_random_key(Block B) { int rc=0; + /* WARNING: + This might need to have the "rc = " removed because this + is VOID in later, and maybe even all, versions. + */ rc = des_random_key(B); return(rc); } @@ -481,6 +485,8 @@ des_new_random_key(Block B) * These function pointers point to the current routines * for encrypting and decrypting data. */ +/* NOTE: These next two might need to have the "static " removed */ + static VOID (*encrypt_output) P((unsigned char *, int)); static int (*decrypt_input) P((int)); diff --git a/ckaaaa.txt b/ckaaaa.txt index 51a7a5b..335ec7d 100644 --- a/ckaaaa.txt +++ b/ckaaaa.txt @@ -1,6 +1,6 @@ -ckaaaa.txt June 2011 +ckaaaa.txt July 2011 - C-KERMIT VERSION 9.0.300 + C-KERMIT VERSION 9.0.301 OVERVIEW OF FILES Communications software for UNIX and (Open)VMS. @@ -26,7 +26,7 @@ DOCUMENTATION C-Kermit is documented in the book "Using C-Kermit", Second Edition, by Frank da Cruz and Christine M. Gianone, Digital Press, ISBN 1-55558-164-1, - supplementated by Web-based updates for C-Kermit 7.0, 8.0, and 9.0. + supplemented by Web-based updates for C-Kermit 7.0, 8.0, and 9.0. PLATFORMS Security @@ -229,7 +229,7 @@ BINARIES If you have FTP access to kermit.columbia.edu (also known as kermit.cc.columbia.edu, ftp.cc.columbia.edu), you can also retrieve various -C-Kermit binaries from the directory kermit/bin/ck*.*, or more conventiently +C-Kermit binaries from the directory kermit/bin/ck*.*, or more conveniently from the web page: http://www.columbia.edu/kermit/ck80binaries.html @@ -355,7 +355,7 @@ otherwise mistake them for Microsoft Word or Windows Help documents. cns: CONNECT command (UNIX only - version that uses select(), not fork()) deb: Debug/Transaction Log formats, Typedefs dia: Modem/Dialer control - fio: System-depdendent File I/O + fio: System-dependent File I/O fns: Protocol support functions fn2: More protocol support functions (and FN3, ...) lib: Common library routines module diff --git a/ckc301.txt b/ckc302.txt similarity index 98% rename from ckc301.txt rename to ckc302.txt index 41b7385..13a661a 100644 --- a/ckc301.txt +++ b/ckc302.txt @@ -305,7 +305,7 @@ worked here, but it wasn't tested in this case. Fixed in getncm(): ckuus5.c, 17 Mar 2003. There are only certain cases where it makes sense to treat doublequotes as -signicant: +significant: . An open quote must be at the beginning or preceded by a space. . A close quote is only at the end or else followed by a space. @@ -337,7 +337,7 @@ makefile ckuver.h ckcmai.c ckclib.c ckcftp.c ckucmd.c ckuus*.c ckutio.c. ---8.0.209--- -From Mark Sapiro, a fix for the March 17th doubleqote fix, getncm(): ckuus5.c, +From Mark Sapiro, a fix for the March 17th doublequote fix, getncm(): ckuus5.c, 4 Apr 2003. From Jeff, 29 Apr 2003: @@ -1149,7 +1149,7 @@ SHELL } agent choice; it does this by setting a new and separate global variable, wildena. Added semantics to ckufio.c. Crude but effective. It might have been more Unixlike to add Yet Another form of quoting but we have enough of that already (later maybe I'll add a \function() for this). -Needs to be propogated to Windows and VMS. 15 Jun 2005. +Needs to be propagated to Windows and VMS. 15 Jun 2005. Improved and fixed typos in HELP WILDCARD and HELP PATTERN. ckuus2.c, 15 Jun 2005. @@ -1224,7 +1224,7 @@ Going back to 1999, I find this: ckedemo.ksc and iftest.ksc. ckucmd.c, ckuus6.c, 27 Sep 99. I undid this change and it made no difference to all the other IF -constructions (in fact, it fixed an urelated one that was broken, so now +constructions (in fact, it fixed an unrelated one that was broken, so now iftest scores 54 out of 54, instead of 53). However, it does not fix the ELSE problem; in fact it pushes it all the way in the other direction: @@ -1355,7 +1355,7 @@ file, that the Solaris 64-bit version of Kermit gets the size correctly, and that it can copy such a file (thus its fopen/fread/fwrite/fclose interface works right). Initiated a large-file transfer between here and Utah over SSH and verified that it puts the correct file size in the A packet when -sending; the right quantites are shown on the file transfer display (file +sending; the right quantities are shown on the file transfer display (file size CPS, percent done, etc). But even at 5Mb/sec, it takes a good while to transfer 4.4GB, more than 2 hours (not streaming; 30 window slots, 4K packets, maybe it would go faster with streaming)... After an hour or so, @@ -1690,7 +1690,7 @@ HP-UX 9.00 builds. This is simply to inhibit the test for whether "long long" is supported by the compiler, since when it isn't, the module containing the test won't compile. makefile, ckuus5.c, 16 Oct 2005. -Making ASKQ always echo askterisks is a bad idea, because when it doesn't +Making ASKQ always echo asterisks is a bad idea, because when it doesn't echo, it's the perfect way to read silently from stdin, e.g. in a CGI script (INPUT can also be used for this but it's not as straightforward). So I put the default for ASKQ back to no echoing, then gave ASKQ its own switch @@ -1857,7 +1857,7 @@ line terminators and byte-stuffing text lines that start with "From ") is slow, 17 sec to read 29 messages totaling 175K. Added INPUT /CLEAR so INPUT can be started with a clean buffer without -requiring a sepearate CLEAR INPUT command. ckuusr.h, ckuus[r24].c, +requiring a separate CLEAR INPUT command. ckuusr.h, ckuus[r24].c, 27 Nov 2005. One thing that INPUT was never able to do well was read and save the @@ -2174,8 +2174,8 @@ the Mac OS X 10.4 version works. ckuus[r367].c, ckcftp.c, 28 Dec 2005. Built on Unixware 7.1.1, a pure 32-bit build, seems fine. Rebuilt on Red Hat AS 4.2 just to make sure I didn't break anything, it's OK. No testing -on HP-UX, etc, because HP testdrive file sytem is full, can't upload anything. -29 Dec 2005. +on HP-UX, etc, because HP testdrive file system is full, can't upload +anything. 29 Dec 2005. Commented out the SHOW FEATURES section that displays constants like INT_MAX, CHAR_MAX, etc, because printing each value in the appropriate @@ -2201,7 +2201,7 @@ does not define _USE_LARGEFILE or _FILE_OFFSET_BITS=64. DIRECTORY BIGFILE shows the size as -1, but if "log debug", it says "no files match", i.e. different behavior, observer effect. I hate when that happens. -Let's see if that's an anomoly... Built on Tru64 Unix 4.0F (64-bit Alpha). +Let's see if that's an anomaly... Built on Tru64 Unix 4.0F (64-bit Alpha). It sees long files just fine. Rebuilt and checked on x86_64 again... fine. OK, let's not worry about IA64 yet. @@ -2419,7 +2419,7 @@ syntax in the bounds pairs results in a null string; missing pieces of the bounds pair result in defaults that should be compatible with previous behavior. ckuus[45].c, ckuusr.h, 13 Jan 2005. -Changed arraybounds() to call boundsdpair(). This was a rather drastic +Changed arraybounds() to call boundspair(). This was a rather drastic change, not strictly necessary, but I think I got all the kinks out. ckuus5.c, 13 Jan 2005. @@ -2755,7 +2755,7 @@ now they all build OK (except can't do NOANSI builds any more on recent Linuxes because of varargs()). ckuus3.c, ckuus5.c, ckuus6.c, ckuus7.c, ckucmd.c, ckcfns.c, 6 May 2006. -Fixed RENAME /LOWER and /UPPER, when given with no colon or agrument, to +Fixed RENAME /LOWER and /UPPER, when given with no colon or argument, to default to ALL. ckuus6.c, 13 May 2006. Built on VMS 7.2-1, tested new RENAME command there; seems to be OK. @@ -2906,7 +2906,7 @@ changing the data type to CK_OFF_T, etc. ckuus6.c, 7 Jul 2006. Noticed that \fkeywordvalue(foo=this is a string) only kept the first word. Fixed it to keep the whole definition. Also added \fkwvalue() as a briefer -synomym. ckuus4.c, 7 Jul 2006 +synonym. ckuus4.c, 7 Jul 2006 Sometimes we want to check if a file's status before we've FOPEN'd it, in which case the channel variable is likely to be empty and \f_status(\%c) @@ -2914,7 +2914,7 @@ would get an error. Making the obvious change didn't fix this, however. It turns out that the function evaluator failed to adjust argn (argument count) when trailing arguments were empty, and argn was being used in this case, and probably others, to test whether an argument existed. I added code to -adjust argn to reflect the number of aruments up to and including the +adjust argn to reflect the number of arguments up to and including the rightmost non-empty one. ckuus4.c, 7 Jul 2006. Fixed \fstripb() to not dump core if second argument is missing. @@ -3093,7 +3093,7 @@ In first case, the asterisk is taken literally; in the third it's a metacharacter and the label matches any string that starts with 'a' and ends with 'z'. -Array initializion would quit early if any initializers were undefined, +Array initialization would quit early if any initializers were undefined, e.g. "decl \&a[] = \%a \%b \%c" would stop at the first element if \%b was not defined, even though \%c might be defined. Fixed in dodcl(): ckuusr.c, 30 Nov 2006. @@ -3241,13 +3241,13 @@ for HP-UX 9. 14 Dec 2006. Changed \fkeywordvalue() to accept a string rather than a single word as its second argument, so that more than one separator could be specified, -and to return -1 on error, 0 if it found nothing, 1 if given a kewyord but +and to return -1 on error, 0 if it found nothing, 1 if given a keyword but no value, and 2 if there was a keyword and a value. dokwval(): ckuus[24].c, 14 Dec 2006. Checked FTP timeout on command channel with FTP DIRECTORY of a big directory using a path into our ftp server that preserves the hanging behavior. The -timeout was actually working, but the failure condition wasn't propogating +timeout was actually working, but the failure condition wasn't propagating back to the user, and there was no error message. Fixed in doftprecv2() and failftprecv2(): ckcftp.c, 15 Dec 2006. @@ -3403,7 +3403,7 @@ works exactly the same way on Linux. Tried today's O_NDELAY method on Solaris. It works perfectly. And then I moved this one to Linux and it works perfectly there too. Except in both -cases we have the wierd thing with Zmodem at the end, but I think that's +cases we have the weird thing with Zmodem at the end, but I think that's because rz/sz don't use standard i/o. On NetBSD, it still hangs at the end. Turns out that testing the pid works in NetBSD, even though it didn't in @@ -3479,7 +3479,7 @@ Maybe ttxin() doesn't have decryption hooks. No, that's not it, the code is there, but the Kermit packet reader does not use ttxin(), it uses ttinl(). But of course we can't use that for external protocols because it's designed only to read Kermit packets. Substituting a loop of ttinc()s for the ttxin() -call fixes things (and stangely enough, it seems to be faster). And now we +call fixes things (and strangely enough, it seems to be faster). And now we have our first external protocol transfer over a secure connection (external Kermit program, Linux over Kerberos 5 to NetBSD). Zmodem worked too for a short file but "something happens" with longer ones. 29 Dec 2006. @@ -3504,7 +3504,7 @@ this are: encrypt_support[cnt]=2 Rebuilding with -DOPENSSL_097 doesn't change anything. Ed Ravin said they -have two different Kerberos installations, Heimdahl and MIT; maybe some +have two different Kerberos installations, Heimdal and MIT; maybe some mixup between the two explains the problem (Jeff concurs). The core dump occurs in ck_crp: encrypt_support(): @@ -3571,7 +3571,7 @@ warnings in the network modules, but they complete. But ck_ssl.c bombed with a conflict between its own declarations of encrypt_output and decrypt_input and the ones in ckuat2.h; removed the prototypes from the latter (as Jeff advised) it built OK and it works OK too. Built with FTP -too, but with link-time warnings about the aformentioned gss_* symbols. +too, but with link-time warnings about the aforementioned gss_* symbols. #ifdef'd them out (gss_mech_krb5, gss_mech_krb5_old, gss_mech_name, and gss_mech_principal) for MACOSX, where these symbols are exported by the library. Now it all compiles and links OK, and runs OK too. 3 Jan 2007. @@ -3772,7 +3772,7 @@ ckupty.c, 9 Jan 2007. Found in HP-UX "man 7 pty" a description of ioctl(fd,TIOCTTY,fc) which is exactly what we want: fc 0 turns off all termio processing and guarantees an -ininterrupted, unmolested, flow-controlled stream of bytes in both +uninterrupted, unmolested, flow-controlled stream of bytes in both directions. This function also exists in Linux, but not in Solaris, NetBSD, or Mac OS X (TIOCNOTTY is not what we want, it does something else entirely). @@ -4362,7 +4362,7 @@ just going in circles. So today I just have to get the code into shape so people could choose among the three alternative routines. The second one, yttyptycmd(), is the one that uses openpty(), which is not portable, so it can be enabled only for Mac OS X, NetBSD, FreeBSD, and Linux, or by also -defining HAVE_OPENTPY at compile time. Anyway, if you build Kermit in the +defining HAVE_OPENPTY at compile time. Anyway, if you build Kermit in the normal way, you get the regular behavior -- ttruncmd() is used to execute external protocols. If you build it with -DXTTPTYCMD, you get the first version of ttptycmd(); with -DYTTPTYCMD the second, and with -DZTTPTYCMD the @@ -4434,7 +4434,7 @@ portability; I've marked them with /* SMS 2007/02/15 */. ckcfns.c, ckcnet.h, ck_ssl.h, ckuus3.c, ckuus4.c, ckvfio.c, ckcftp.c, ckvker.mms (which was rewritten to actually reflect the source module dependencies), ckvker.com (also heavily modified). ckvker.com (the "makefile" for VMS -C-Kermit) now indludes "F" and "I" option flags for the large File and +C-Kermit) now includes "F" and "I" option flags for the large File and Internal ftp features, plus better handling of Vax/Alpha/IA64 distinction. 26 Feb 2007. @@ -4486,11 +4486,11 @@ now supports case-sensitive file systems, and so it can't find anything. Workaround: bypass MMS (include "m" in P1). With this, "@ckvker.com ifm" builds OK on HP Testdrive, but I can't test the new features since outbound connections are not allowed there. As for fseeko(), ftello(), and utime(), -they simply are not availble prior to VMS 7.3. It would probably be a good +they simply are not available prior to VMS 7.3. It would probably be a good idea to test for this in CKVKER.COM, but actually it is possible to install newer C's and CRTLs on older VMS versions, so don't stand in their way. -28 Feb 2007: With additional chages from SMS, and then some further +28 Feb 2007: With additional changes from SMS, and then some further adjustments, I was able to build the FTP version on VMS 7.2-1. First I tested it with GET of a binary file, but it transferred it in text mode. After a few more attempts with PUT and GET, it crashed with "floating/decimal @@ -5004,7 +5004,7 @@ from the ttpty.c episode, I uncommented it. But still: . sz txt (zst): Fails ("Got ZCAN") . sz bin (zsb): Fails instantly (but with no diagnostic) . rz txt (zrt): OK - . rz bin (zrb): Fails with tons of "Bad CRC", "Gargage Count exceeded" + . rz bin (zrb): Fails with tons of "Bad CRC", "Garbage Count exceeded" Conclusion for the day: I think this is hopeless. Even if I can get it to work somewhere, the results depend on the exact Zmodem software, how it uses @@ -5179,7 +5179,7 @@ Also: "ckuusx.c", line 9232: warning: implicit function declaration: creat -This is called in the IKSD dababase code, used for getting a lockfile. +This is called in the IKSD database code, used for getting a lockfile. creat() is a Unixism in code that is supposed to be portable. But IKSD only runs on Unix and Windows, so I assume the Windows C library has a creat() function. Anyway, suddenly the Solaris header files seem to have blocked @@ -5259,7 +5259,7 @@ two: As a first cut I did this simply by replacing the contents of the #ifdef CK_REDIR section of the latter with that of the former. Of course in -Solaris this comes up with openty() implicitly declared at compile time and +Solaris this comes up with openpty() implicitly declared at compile time and unresolved at link time. So the first task is to get HAVE_OPENPTY defined for platforms that have it and have the others use the ttruncmd(). For starters I put an #ifdef block in ckcdeb.h that defines HAVE_OPENPTY for @@ -5519,7 +5519,7 @@ ttptycmd() is better in every respect than ttruncmd() except in speed Let's see if ttyptycmd still works in remote mode (to local K95): . sz / text works, but slowly. - . lsz / text works but some wierd errors are reported. + . lsz / text works but some weird errors are reported. . lsz / binary / no IAC doesn't work at all (CRC-32 mismatch for a header; Unexpected control character ignored: 13, etc). . sz / binary / no IAC works OK but slow. @@ -5582,7 +5582,7 @@ exceeds, say, 1MB, the chances of successful completion go way down, independent of whether my external protocol is rz or lrz. I like lrz better because the error reports come out on the screen as the transfer is going on. Trying to download a real-world binary file -- a 2.2MB C-Kermit -executable -- I get 4500 error messages but the transfer evenually succeeds, +executable -- I get 4500 error messages but the transfer eventually succeeds, with an effective throughput of 21Kcps. Actually it turns out that "sz -a somebigtextfile" (2.2MB) also gets a lot @@ -6094,7 +6094,7 @@ needs -DNO_KRB5_INIT_ETS". Makefile, 3 Mar 2009. Fixed copyright date announced in herald, ckuus5.c, 3 Mar 2009. -Patch from Seth Therault to avoid deprecation warning for utmp references +Patch from Seth Theriault to avoid deprecation warning for utmp references in ckufio.c in Mac OS X 10.5 (later, this became a consolidated makefile target that works automatically for at least Mac OS X 10.3.9 through 10.5.6). makefile, ckufio.c, 28 April 2009. @@ -6121,7 +6121,7 @@ From Jason Lehr. makefile, 27 May 2009. Updated the linux+openssl+zlib+shadow+pam target to chain to the new main Linux target. A bunch of other ones remain un-updated. makefile, 12 Jun 2009. -Updates to the new Mac OS X 10.5 target from Seth Therault (which is +Updates to the new Mac OS X 10.5 target from Seth Theriault (which is supposed to work on all Mac OS 10-point-anything) to avoid warnings that came up on on Mac OS 10.4.11/Intel. Once this one is proven we should be able to remove/consolidate lots of other ones. makefile, 12 Jun 2009. @@ -6205,7 +6205,7 @@ C-Kermit using Sun CC rather than gcc. makefile, 4 Sep 2009. Tried building on HP-UX 10.20, bundled (non-ANSI) compiler ("make hpux1000"). This failed until I: - . Moved a struct inititialization out of setextern(), ckuus3.c. + . Moved a struct initialization out of setextern(), ckuus3.c. . Removed an ANSIism from the declaration of sigchld_handler() in ckutio.c . Added a cast to strcmp() in zvuser(), ckufio.c. @@ -6470,7 +6470,7 @@ builds. ckuus6.c, 14 Oct 2009. SHOW PROTOCOL code for external protocols had to be #ifdef'd out for -DNOPUSH builds. ckuus4.c, 14 Oct 2009. -There was some confusion between "No XYZMODEM" and "No extermal protocols"; +There was some confusion between "No XYZMODEM" and "No external protocols"; cleared up in ckuus3.c, 14 Oct 2009. After all that, 86 different combinations of feature selections built OK on @@ -6571,7 +6571,7 @@ put every single 8-bit value into the include set, e.g. (for a TSV file): I changed cksplit() to treat all 8-bit bytes 128-255 as non-break characters by default. It might have made more sense to do this for 160-255 (since -128-159 are traditionaly C1 control characters) but thanks to Microsoft +128-159 are traditionally C1 control characters) but thanks to Microsoft tradition is out the window. To treat one or more 8-bit characters as break characters, put them in the break set. This might break some scripts, but I doubt it because this flaw was so awful that if anyone had come up against @@ -6676,7 +6676,7 @@ instead, C-Kermit returns immediately to its prompt. 27 Nov 2009. It could simply be that some of the buffers we allocate are much bigger now. But again, I don't see much difference between 8.0.211 and 9.0; we were already allocating 32K command-related buffers (malloc() takes a size_t, and -size_t is an int almost everywere). I built the same source on NetBSD and +size_t is an int almost everywhere). I built the same source on NetBSD and ran the same script (with \fqueeze()), and it worked fine. Let's worry about this later, if it comes up. 27 Nov 2009. @@ -7187,7 +7187,7 @@ can mess up the input file. For safety FCLOSE has to require a channel number or ALL. ckuus7.c, 4 Aug 2010. Added \fstrcmp(s1,s2,case,start,length), which has the advantage over IF -EQU,LGT,LLT that case senstivity can be specified as a function arg, and +EQU,LGT,LLT that case sensitivity can be specified as a function arg, and also substrings can be specified. ckuusr.h, ckuus[24].c, 5 Aug 2010. The CSV feature of Alpha.06 had a subtle flaw, namely that if the last item @@ -7325,13 +7325,13 @@ as the CRC, match the packet contents, then we accept the packet and switch to BLOCK 5 mode. On the other hand, if the "5" was put there by corruption, the CRC should -catch the error. In that case we NAK the packet and presumabely get a +catch the error. In that case we NAK the packet and presumably get a different version back. There would be no reason to try to re-read the same packet with a different block check, because the "5" could not possibly be there legitimately unless it had a 3-byte CRC. To be clear, this is cheating. We read the packet contents before we know the packet is correct, then we check that it *is* correct. I made the 4-line change to rpack() -and it works OK in the absense of transmission errors. ckcfn2.c, 3 Jun 2011. +and it works OK in the absence of transmission errors. ckcfn2.c, 3 Jun 2011. So the various combinations should work as desired: @@ -7736,7 +7736,7 @@ transfer the gzipped C-Kermit tarball. Kermit to the rescue. 19 Jun 2011. Transferred the tarball over serial ports to SCO OSR5.0.5 at 38.4Kbps, the highest speed supported, 12 minutes, no errors, 3300cps. Unpack, make sco32v505udk, OK. Also built the TCP/IP version and it almost made an -outbound connection, but only once (not a Kermit program but something with +outbound connection, but only once (not a Kermit problem but something with the TCP/IP stack). 19 Jun 2011. Ditto for Solaris 2.6/i386, except 57.6Kbps, 4K-byte packets, no problem. @@ -7837,5 +7837,45 @@ Updated version text and date. ckcmai.c, makefile, 11 July 2011. --- C-Kermit 9.0.301 --- +After the initial release I made some small changes that affect only HP-UX +5.x: added -DVOID=void and -DCKVOID=void to the hpux0500 makefile targets, +and put #ifdefs around #include , which (in the WinTCP case) didn't +protect itself against multiple inclusion (which is happening in other +header files, not in Kermit). makefile, ckucmd.c, ckucon.c, ckutio.c, +ckufio.c, ckcnet.c, ckcftp.c, 14 July 2011. + +In the new copyright notice, copied from the BSD license template, +one instance of "the " was not replaced by "Columbia +University". Fixed in ckcmai.c, 19 July 2011. + +Added another search term for lk5crypto in the linux+krb5 targets. +makefile, 20 July 2011. + +Added and successfully used a new solaris9+krb5+ssl target. +makefile, 8 Aug 2011. + +FreeBSD 9 switched from utmp to utmpx, which broke compilation of Kermit on +that version. Furthermore, the UUCP lockfile convensions changed in FreeBSD +8, which did not prevent C-Kermit from compiling, but any attempt to lock a +terminal or pty device would fail. Thanks to Alexey Dokuchaev "danfe" for +finding and patching the problems. I undid the patches and fixed the code +so it didn't need to be patched, except for some declarations in the +ck_crp.c module, which I felt had better not be changed without thoroughly +testing the changes on dozens of different platforms, which I don't have +time to do (in any case, it builds OK on FreeBSD 9 without the patch). In +particular I made completely new makefile targets for FreeBSD 4.0 and later, +which automatically detect FreeBSD 8 and FreeBSD 9 to enable the appropriate +feature tests in the code, for a regular build and a build with OpenSSL. +These changes should affect only FreeBSD. ckutio.c, ckufio.c, ck_crp.c, +ckuus5.c, makefile, 20 Aug 2011. + +Changed the version to 9.0.302, ckcmai.c, 20 Aug 2011. + +Fixed freebsd+ssl and netbsd+ssl, netbsd+krb5, and netbsd+krb5+ssl targets +to have CC=$(CC) instead of CC=gcc; ditto for CC2, and adjusted line breaks +in freebsd and freebsd+ssl targets. makefile, 21 Aug 2011. + +--- 9.0.302 --- + --------------------------------- *************************** diff --git a/ckcbwr.txt b/ckcbwr.txt index b33b5c1..533c946 100644 --- a/ckcbwr.txt +++ b/ckcbwr.txt @@ -129,9 +129,9 @@ CONTENTS command or program. The built-in command might not behave the way the platform-specific external one did, but many options are available for customization. Of course the underlying - platform-specific command can still be accesssed with "!", "@", or + platform-specific command can still be accessed with "!", "@", or "RUN" wherever the installation does not forbid. In UNIX, the "ls" - command can be accesssed directly as "ls" in C-Kermit. + command can be accessed directly as "ls" in C-Kermit. * SEND ? prints a list of switches rather than a list of filenames. If you want to see a list of filenames, use a (system-dependent) construction such as SEND ./? (for UNIX, Windows, or OS/2), SEND @@ -469,11 +469,11 @@ The SSH Client software. Such drivers are generally NOT available in UNIX or other non-Windows (or non-OS/2, in the case of the Mwave) platforms. - In order to dial a modem, C-Kermit must know its repertoire of commands - and responses. Each modem make and model is likely to have a different - repertoire. Since Kermit has no way of knowhing which kind of modem - will be dialed, normally you have to tell it with a SET MODEM TYPE - command, e.g.: + In order to dial a modem, C-Kermit must know the modem's repertoire of + commands and responses. Each modem make and model is likely to have a + different repertoire. Since Kermit has no way of knowing which kind of + modem will be dialed, normally you have to tell it with a SET MODEM + TYPE command, e.g.: set modem type usrobotics set line /dev/cua0 @@ -486,7 +486,7 @@ The SSH Client configuration includes error correction, data compression, and hardware (RTS/CTS) flow control. As long as C-Kermit is capable of hardware flow control (as it is on many, but not all, the platforms where it runs, - since some operating systems don't support it), the modem can be dailed + since some operating systems don't support it), the modem can be dialed immediately, without lengthy configuration dialogs, and in fact this is what SET MODEM TYPE GENERIC-HIGH-SPEED does. In C-Kermit 8.0, GENERIC-HIGH-SPEED has become the default modem type, so now it is @@ -860,7 +860,7 @@ The SSH Client an escape sequence like " O p"). In both cases, C-Kermit has no way to tell the difference between such multibyte key values, and the corresponding series of single-byte key values. This could only be done - by accesssing the keyboard at a much lower level in a highly + by accessing the keyboard at a much lower level in a highly platform-dependent manner, probably requiring tens of thousands of lines of code to support even a sampling of the most popular workstation / OS combinations. @@ -983,7 +983,7 @@ SEND /COMMAND [ other switches such as /AS-NAME: ] command [ arguments... ] transfer fails because Kermit will not rename a directory. Send the file with another name, or use SET FILE COLLISION RENAME. * If the directory lacks write permission, the file transfer fails - even if you have write accesss to the file that is being backed up; + even if you have write access to the file that is being backed up; in that case, switch to SET FILE COLLISION OVERWRITE or APPEND, or send to a different directory. @@ -1077,7 +1077,7 @@ setmaps -t NOMAP must SET FLOW NONE. The HP48SX does not support flow control, and evidently also becomes confused if you attempt to use it. You might also need to use SET SEND PAUSE 100 (or other number). For greater - detail about transferring files the the HP-48, see: + detail about transferring files the HP-48, see: [85]http://www.columbia.edu/kermit/hp48.html @@ -1355,7 +1355,7 @@ setmaps -t NOMAP interruption characters between every packet. The "What Are You" response is sitting in the keyboard buffer. Eventually Kermit will read a character such as "c" that is a valid interruption - character, and the file transfer stops with "User cancelled". + character, and the file transfer stops with "User canceled". The right way to handle this situation is to have your look for the "What Are You?" sequence and send the response itself, as described in @@ -1398,8 +1398,8 @@ echo \fn2hex(\%x) By the way, you might be tempted to use Kermit's \xnn notation to plug hex numbers into arithmetic expressions but this doesn't work. That - notation is stricly for bytes (hex representation of character values), - not for numbers. + notation is strictly for bytes (hex representation of character + values), not for numbers. 11.11. Other... diff --git a/ckccfg.txt b/ckccfg.txt index f27d56e..0185c3d 100644 --- a/ckccfg.txt +++ b/ckccfg.txt @@ -440,7 +440,7 @@ C-Kermit Configuration Options NOFRILLS 1918966 9.8% No "frills". NOFTP 1972496 7.3% No FTP client. NODIAL 1984488 6.7% No automatic modem dialing. - NOPUSH 2070184 2.7% No shell accesss, running external programs, etc. + NOPUSH 2070184 2.7% No shell access, running external programs, etc. NOIKSD 2074129 2.5% No Internet Kermit Server capability. NOHTTP 2082610 2.1% No HTTP client. NOFLOAT 2091332 1.7% No floating-point arithmetic. @@ -541,7 +541,7 @@ C-Kermit Configuration Options supports higher levels of optimization (e.g. -O2 or higher number, -Onolimit (HP-UX), etc), try them; the greater the level of optimization, the longer the compilation and more likely the - compiler will run out of memory. The the latter eventuality, some + compiler will run out of memory. The latter eventuality, some compilers also provide command-line options to allocate more memory for the optimizer, like "-Olimit number" in Ultrix. b. If your platform supports shared libraries, change the make entry @@ -699,7 +699,7 @@ C-Kermit Configuration Options then to let selected users or services get through after all. One firewall method is called SOCKS, in which a proxy server allows - users inside a firewall to accesss the outside world, based on a + users inside a firewall to access the outside world, based on a permission list generally stored in a file. SOCKS is enabled in one of two ways. First, the standard sockets library is modified to handle the firewall, and then all the client applications are relinked (if @@ -1017,7 +1017,7 @@ C-Kermit Configuration Options immediately, rather than returning to its prompt. NOPUSH and NOCCTRAP together allow Kermit to be run from restricted - shells, preventing accesss to system functions. + shells, preventing access to system functions. [ [140]C-Kermit Home ] [ [141]Kermit Home ] @@ -1358,7 +1358,7 @@ C-Kermit Configuration Options MAXRP=number Maximum receive-packet length. MAXSP=number Maximum send-packet length. MDEBUG Malloc-debugging requested. - MINIDIAL Minimum modem dialer support: CCITT, Hayes, Unkown, and None. + MINIDIAL Minimum modem dialer support: CCITT, Hayes, Unknown, and None. MINIX Build for MINIX. MIPS Build for MIPS workstation. MULTINET Build with support for TGV MultiNet TCP/IP (VAX/VMS). @@ -1368,7 +1368,7 @@ C-Kermit Configuration Options NDIR BSD long filenames supported using and opendir(). NDGPWNAM Don't declare getpwnam(). NDSYSERRLIST Don't declare sys_errlist[]. - NEEDSELECTDEFS select() is avaible but we need to define FD_blah + NEEDSELECTDEFS select() is available but we need to define FD_blah ourselves. NETCMD Build with support for SET HOST /COMMAND and PIPE commands. NEXT Build for NeXT Mach 1.x or 2.x or 3.0, 3.1, or 3.2. @@ -1512,8 +1512,7 @@ C-Kermit Configuration Options SVR3 Build for AT&T System V Release 3. SVR3JC Allow job control support on System V Release 3 UNIX versions. SVR4 Build for AT&T System V Release 4. - SW_ACC_ID UNIX only -- swap real & effective ids around accesss() - calls. + SW_ACC_ID UNIX only -- swap real & effective ids around access() calls. sxaE50 Build for PFU Compact A Series SX/A TISP. SYSLOGLEVEL=n Force syslogging at given level. SYSTIMEH Include . diff --git a/ckcftp.c b/ckcftp.c index 7667940..66c7940 100644 --- a/ckcftp.c +++ b/ckcftp.c @@ -2,7 +2,7 @@ /* C K C F T P -- FTP Client for C-Kermit */ -char *ckftpv = "FTP Client, 9.0.259, 15 Jun 2011"; +char *ckftpv = "FTP Client, 9.0.260, 14 Jul 2011"; /* Authors: @@ -183,7 +183,15 @@ extern int TlsIndex; #include #endif /* def VMS [else] */ #include -#include + +#ifndef HPUXPRE65 +#include /* Error number symbols */ +#else +#ifndef ERRNO_INCLUDED +#include /* Error number symbols */ +#endif /* ERRNO_INCLUDED */ +#endif /* HPUXPRE65 */ + #ifndef NOTIMEH #include #endif /* NOTIMEH */ diff --git a/ckcmai.c b/ckcmai.c index 065fb67..a5640e5 100644 --- a/ckcmai.c +++ b/ckcmai.c @@ -1,6 +1,6 @@ -#define EDITDATE "11 Jul 2011" /* Last edit date dd mmm yyyy */ -#define EDITNDATE "20110711" /* Keep them in sync */ -/* Mon Jul 11 09:23:48 2011 */ +#define EDITDATE "20 Aug 2011" /* Last edit date dd mmm yyyy */ +#define EDITNDATE "20110820" /* Keep them in sync */ +/* Sat Aug 20 17:20:17 2011 */ /* ckcmai.c - Main program for C-Kermit plus some miscellaneous functions */ @@ -64,7 +64,7 @@ char *ck_s_date = EDITDATE; /* See top */ char *buildid = EDITNDATE; /* See top */ #ifdef UNIX -static char sccsid[] = "@(#)C-Kermit 9.0.301"; +static char sccsid[] = "@(#)C-Kermit 9.0.302"; #endif /* UNIX */ /* @@ -78,8 +78,8 @@ static char sccsid[] = "@(#)C-Kermit 9.0.301"; for future releases. */ -char *ck_s_ver = "9.0.301"; /* C-Kermit version string */ -long ck_l_ver = 900301L; /* C-Kermit version number */ +char *ck_s_ver = "9.0.302"; /* C-Kermit version string */ +long ck_l_ver = 900302L; /* C-Kermit version number */ #ifdef OS2 char *ck_s_xver = "3.0.0"; /* Product-specific version string */ @@ -168,7 +168,7 @@ char *copyright[] = { " the documentation and/or other materials provided with the", " distribution.", " ", -" + Neither the name of the nor the names of its", +" + Neither the name of Columbia University nor the names of its", " contributors may be used to endorse or promote products derived", " from this software without specific prior written permission.", " ", diff --git a/ckcnet.c b/ckcnet.c index 5384e00..2bb01a6 100644 --- a/ckcnet.c +++ b/ckcnet.c @@ -1,9 +1,9 @@ -char *cknetv = "Network support, 9.0.296, 16 Mar 2010"; +char *cknetv = "Network support, 9.0.297, 14 Jul 2011"; /* C K C N E T -- Network support */ /* - Copyright (C) 1985, 2010, + Copyright (C) 1985, 2011, Trustees of Columbia University in the City of New York. All rights reserved. See the C-Kermit COPYING.TXT file or the copyright text in the ckcmai.c module for disclaimer and permissions. @@ -258,7 +258,13 @@ struct timezone { #endif /* OSF13 */ #ifndef I386IX -#include /* Already included above */ +#ifndef HPUXPRE65 +#include /* Error number symbols */ +#else +#ifndef ERRNO_INCLUDED +#include /* Error number symbols */ +#endif /* ERRNO_INCLUDED */ +#endif /* HPUXPRE65 */ #endif /* I386IX */ #include /* Everybody needs this */ diff --git a/ckcplm.txt b/ckcplm.txt index fc7595a..e00edde 100644 --- a/ckcplm.txt +++ b/ckcplm.txt @@ -231,7 +231,7 @@ foo(x,y) int x, y; { be selected by defining a symbol, which, if not defined, leaves the program exactly as it was before the changes. * Although it might be possible to "clean up" the "#ifdef mess", - nobody has accesss to all the hundreds of platforms served by the + nobody has access to all the hundreds of platforms served by the #ifdefs to check the results. And to answer the second-most-oft-repeated question: "Why don't you @@ -961,7 +961,7 @@ foo(x,y) int x, y; { calling and return conventions, and has the same type. The Group E modules contain both functions and global variables that - are accesssed by modules in the other groups. These are now described. + are accessed by modules in the other groups. These are now described. (By the way, I got this list by linking all the C-Kermit modules together except ckutio and ckufio. These are the symbols that ld @@ -1082,7 +1082,7 @@ foo(x,y) int x, y; { char *dftty; Default communication device. Set by Group E module. Used in - many places. This variable should be initialized the the symbol + many places. This variable should be initialized the symbol CTTNAM, which is defined in ckcdeb.h, e.g. as "/dev/tty" for UNIX, "TT:" for VMS, etc. Example: char *dftty = CTTNAM; @@ -1147,7 +1147,7 @@ foo(x,y) int x, y; { #define ZSYSFN 8 /* Input from a system function (pipe) */ #define ZRFILE 9 /* Local file for READ command */ (NEW) #define ZWFILE 10 /* Local file for WRITE command */ (NEW) - #define ZMFILE 11 /* Auxilliary file for internal use */ (NEW) + #define ZMFILE 11 /* Auxiliary file for internal use */ (NEW) #define ZNFILS 12 /* How many defined file numbers */ In the descriptions below, fn refers to a filename, and n refers to one @@ -1244,8 +1244,7 @@ foo(x,y) int x, y; { Check to see if file with name fn is a regular, readable, existing file, suitable for Kermit to send -- not a directory, not a symbolic link, etc. Returns: - -3: if file exists but is not accesssible (e.g. - read-protected); + -3: if file exists but is not accessible (e.g. read-protected); -2: if file exists but is not of a readable type (e.g. a directory); -1: on error (e.g. file does not exist, or fn is garbage); @@ -1261,7 +1260,7 @@ foo(x,y) int x, y; { long zgetfs(fn) char *fn; - Gets the size of the given file, regardless of accesssibility. + Gets the size of the given file, regardless of accessibility. Used for directory listings. Unlike zchki(), should return the size of any kind of file, even a directory. zgetfs() also should serve as a mini "get file info" function that can be used until @@ -1384,9 +1383,9 @@ foo(x,y) int x, y; { int zsetroot(char * dir) - Sets the root for the user's file accesss, like Unix chroot(), + Sets the root for the user's file access, like Unix chroot(), but does not require privilege. In Unix, this must be - implemented entirely by Kermit's own file accesss routines. + implemented entirely by Kermit's own file access routines. Returns: 1: Success -1: Invalid argument @@ -1741,7 +1740,7 @@ foo(x,y) int x, y; { int zxcmd(n,s) char *s; - Runs a system command so its output can be accesssed as if it + Runs a system command so its output can be accessed as if it were file n. The command is run in ordinary, unprivileged user mode. If n is ZSTDIO or ZCTERM, returns -1. @@ -1813,7 +1812,7 @@ foo(x,y) int x, y; { isn't. Makes any appropriate system log entries (IKSD logins, failed login attempts, etc). If password is valid, logs the user in as herself (if real user), or sets up restricted anonymous - accesss if user is guest (e.g. changes file-system root to + access if user is guest (e.g. changes file-system root to anonroot and sets isguest = 1). VOID @@ -1835,14 +1834,14 @@ foo(x,y) int x, y; { installed to prevent such security breaches by turning off the program's special privileges at all times except when they are needed. - In UNIX, the only need Kermit has for privileged status is accesss to + In UNIX, the only need Kermit has for privileged status is access to the UUCP lockfile directory, in order to read, create, and destroy lockfiles, and to open communication devices that are normally protected against the user (see the [133]Unix C-Kermit Installation Instructions for discussion). Therefore, privileges should only be enabled for these operations and disabled at all other times. This relieves the programmer of the responsibility of putting expensive and - unreliable accesss checks around every file accesss and subprocess + unreliable access checks around every file access and subprocess creation. Strictly speaking, these functions are not required in all C-Kermit @@ -1889,7 +1888,7 @@ foo(x,y) int x, y; { Attempts to turns privileges off in such a way that they can be turned on again later. Then checks to make sure that they were really turned off. If they were not really turned off, then they - are cancelled permanently. Returns: + are canceled permanently. Returns: 0 on success nonzero on failure @@ -2061,9 +2060,9 @@ foo(x,y) int x, y; { int ttclos() Closes the communication device (tty or network). If there were - any kind of exclusive accesss locks connected with the tty, - these are released. If the tty has a modem connection, it is - hung up. For true tty devices, the original tty device modes are + any kind of exclusive access locks connected with the tty, these + are released. If the tty has a modem connection, it is hung up. + For true tty devices, the original tty device modes are restored. Returns: -1: on failure. 0: on success. @@ -2267,9 +2266,9 @@ foo(x,y) int x, y; { <=0: no timer, wait forever (e.g. for incoming call). For real tty devices, ttopen() attempts to gain - exclusive accesss to the tty device, for example in + exclusive access to the tty device, for example in UNIX by creating a "lockfile" (in other operating - systems, like VMS, exclusive accesss probably + systems, like VMS, exclusive access probably requires no special action). Side effects: @@ -2283,8 +2282,8 @@ foo(x,y) int x, y; { Returns: 0: on success -5: if device is in use - -4: if accesss to device is denied - -3: if accesss to lock mechanism denied + -4: if access to device is denied + -3: if access to lock mechanism denied -2: upon timeout waiting for device to open -1: on other error @@ -2880,7 +2879,7 @@ I.1. Format of System-Dependent File Permissions in A-Packets For UNIX (System ID = U1), it's the familiar 3-digit octal number, the low-order 9 bits of the filemode: Owner, Group, World, e.g. 660 = - read/write accesss for owner and group, none for world, recorded as a + read/write access for owner and group, none for world, recorded as a 3-digit octal string. High-order UNIX permission bits are not transmitted. diff --git a/ckermit70.txt b/ckermit70.txt index 795db1c..a796cfd 100644 --- a/ckermit70.txt +++ b/ckermit70.txt @@ -12,7 +12,7 @@ For C-Kermit 7.0 As of C-Kermit version: 7.0.196 This file created: 8 February 2000 This file last updated: -Mon Sep 13 08:52:41 2010 +Mon Aug 8 10:39:18 2011 Authors: Frank da Cruz and Christine M. Gianone @@ -650,9 +650,9 @@ II. NEW FEATURES command or program. The built-in command might not behave the way the platform-specific external one did, but many options are available for customization. Of course the underlying - platform-specific command can still be accesssed with "!", "@", or + platform-specific command can still be accessed with "!", "@", or "RUN" wherever the installation does not forbid. In UNIX, the "ls" - command can be accesssed directly as "ls" in C-Kermit. See + command can be accessed directly as "ls" in C-Kermit. See [352]Section 4.5.1 for details. 7. SEND ? prints a list of switches rather than a list of filenames. If you want to see a list of filenames, use a (system-dependent) @@ -2289,11 +2289,11 @@ II. NEW FEATURES As of C-Kermit 7.0, in the UNIX version only, the COPY and RENAME commands are built in and do not call the underlying platform's COPY or RENAME command. This allows them to work in "NOPUSH" versions and other - circumstances where it can't accesss system commands, and it allows - file copying and renaming to be done portably in scripts. The + circumstances where it can't access system commands, and it allows file + copying and renaming to be done portably in scripts. The characteristics of the built-in COPY or RENAME include: * It fails if the source file is a directory or is wild or lacks read - accesss. + access. * It fails if the source file is the destination file. * It allows the destination file to be a directory, in which case the source file is copied (or renamed) into it with the same name. @@ -2332,12 +2332,12 @@ II. NEW FEATURES 1.18. The MANUAL Command - The MANUAL command can be used to accesss the appropriate Kermit manual + The MANUAL command can be used to access the appropriate Kermit manual or other manual. The general syntax is: MANUAL [ string ] If the string is omitted, C-Kermit asks the underlying system to - accesss the C-Kermit manual using whatever method is appropriate + access the C-Kermit manual using whatever method is appropriate for the system. The specific action depends on the system. In UNIX, a "man" command is @@ -2516,13 +2516,13 @@ Compiled Dec 31 1999 10:38:54, options: 1. Only one READ file and one WRITE file can be open at a time. 2. The READ and WRITE commands are strictly line oriented. 3. These commands can not be used with binary files. - 4. They do not support read/write accesss or random accesss. + 4. They do not support read/write access or random access. 5. The syntax is a bit counterintuitive for programmers. The new file i/o system allows multiple files to be open at once, in any desired combination of modes (read/write/append) supported by the operating system, for line, block (record), or character i/o, for - sequential or random accesss, using consistent syntax and conventions. + sequential or random access, using consistent syntax and conventions. The new system, however, does not replace the old one, since the old system still must be used for: @@ -2582,8 +2582,8 @@ Compiled Dec 31 1999 10:38:54, options: The command to open a file is: FILE OPEN [ switches ] variable filename - Opens a file for the type of accesss specified by the switches, - or for read-only accesss if no switches are given. Upon success, + Opens a file for the type of access specified by the switches, + or for read-only access if no switches are given. Upon success, a channel number is assigned to this file and stored in the given variable so you can refer to the open file in subsequent i/o commands. If the file can not be opened, the FILE OPEN @@ -2592,9 +2592,9 @@ Compiled Dec 31 1999 10:38:54, options: The FILE OPEN switches are: /READ - Open the file for read accesss. If no switches are given, /READ + Open the file for read access. If no switches are given, /READ is assumed. If the file does not exist or can't be opened for - read accesss, the FILE OPEN command fails. + read access, the FILE OPEN command fails. /WRITE Allow writing. If a file of the same name already exists, it is @@ -2614,7 +2614,7 @@ Compiled Dec 31 1999 10:38:54, options: switch is meaningless (but still can be used) in UNIX. In VMS, Windows, and OS/2, it inhibits end-of-line processing and conversion, and so should be used for binary files and/or files - that are to be accesssed in record or character mode rather than + that are to be accessed in record or character mode rather than line by line. The variable for the channel number can be any kind of variable: the @@ -3046,10 +3046,10 @@ Compiled Dec 31 1999 10:38:54, options: The loop works because a relative SEEK outside the file fails. - It is also possible to use block i/o to manage random-accesss files - with fixed-length records (as long as they don't contain NUL - characters). Suppose, for example, you have a file of "card image" - records with fixed-field information about customers, such as: + It is also possible to use block i/o to manage random-access files with + fixed-length records (as long as they don't contain NUL characters). + Suppose, for example, you have a file of "card image" records with + fixed-field information about customers, such as: Name: Columns 1-32 (column numbers are 1-based) Address: Columns 33-72 @@ -4106,7 +4106,7 @@ define HSDIAL { ; High Speed DIAL set dial macro xxx dial xyzcorp - This defines a DIAL MACRO called xxx, which puts an accesss code on the + This defines a DIAL MACRO called xxx, which puts an access code on the front of the number. Another example might be: def xxx if equal "\v(modem)" "hayes-1200" return \freplace(\%1,$,{,,,,,}) @@ -4143,11 +4143,11 @@ define HSDIAL { ; High Speed DIAL be busy. To illustrate the final item, suppose you have a choice among many - phone service providers; the provider is chosen by dialing an accesss + phone service providers; the provider is chosen by dialing an access code before the number. Different providers might be better (e.g. cheaper) for certain times of day or days of the week, or for dialing - certain locations; you can use the DIAL macro to add the accesss for - the most desirable provider. + certain locations; you can use the DIAL macro to add the access for the + most desirable provider. Similarly, when the same number might be reached through multiple providers, it's possible that one provider might not be able to @@ -4646,7 +4646,7 @@ define HSDIAL { ; High Speed DIAL disabled. SET TELNET ENVIRONMENT DISPLAY is used to set the DISPLAY variable that - is sent to the host, as well as the the XDISPLAY location. + is sent to the host, as well as the XDISPLAY location. 2.3.5. Connecting to Raw TCP Sockets @@ -4968,7 +4968,7 @@ SET HOST /PTY {sh -c "grep somestring *.txt"} Although C-Kermit includes its own Telnet implementation, you might need to use an external Telnet program to make certain connections; - perhaps because it has accesss or security features not available in + perhaps because it has access or security features not available in C-Kermit itself. As noted above, the only precautions necessary are usually: @@ -5238,7 +5238,7 @@ SET HOST /PTY {sh -c "grep somestring *.txt"} set host /server * if fail stop 1 X.25 "set host *" failed - And then accesss it from the client as follows: + And then access it from the client as follows: set network type x.25 if fail stop 1 Sorry - no X.25 support @@ -5459,7 +5459,7 @@ SET HOST /PTY {sh -c "grep somestring *.txt"} open any dialout device when its open count indicates that another process has it open. SHOW COMM (in QNX only) displays the setting, and if you have a port open, it also shows the current open count (with - C-Kermit's own accesss always counting as 1). + C-Kermit's own access always counting as 1). 2.12. The Connection Log @@ -5552,10 +5552,10 @@ SET HOST /PTY {sh -c "grep somestring *.txt"} On multiuser systems, it is possible to keep a single, shared, system-wide connection log, but this is not recommended since (a) it - requires you keep a publicly write-accesssible logfile (a glaring - target for mischief), and (b) it would require each user to log to that - file and not disable logging. A better method for logging connections, - in UNIX at least, is syslogging (see [429]ckuins.txt Section 15 and + requires you keep a publicly write-accessible logfile (a glaring target + for mischief), and (b) it would require each user to log to that file + and not disable logging. A better method for logging connections, in + UNIX at least, is syslogging (see [429]ckuins.txt Section 15 and [430]Section 4.2 of the [431]IKSD Administration Guide for details). 2.13. Automatic Connection-Specific Flow Control Selection @@ -5792,7 +5792,7 @@ SET HOST /PTY {sh -c "grep somestring *.txt"} Make an secure private connection with SSL (only if SSL support is included in your version of Kermit). In this case the port name might need to be https rather than http, e.g. "set host - secureserver.xyxcorp.com https /ssl". + secureserver.xyzcorp.com https /ssl". /TLS Make an secure private connection with TLS (only if TLS support @@ -5830,10 +5830,10 @@ SET HOST /PTY {sh -c "grep somestring *.txt"} eight headers may be specified. /USER:name - In case a page requires a username for accesss. + In case a page requires a username for access. /PASSWORD:password - In case a page requires a password for accesss. + In case a page requires a password for access. /ARRAY:arrayname Tells Kermit to store the response headers in the given array, @@ -5943,7 +5943,7 @@ SET HOST /PTY {sh -c "grep somestring *.txt"} As noted in the manual, C-Kermit's CONNECT command on UNIX is not a terminal emulator, but rather a "semitransparent pipe" between the - terminal or emulator you are using to accesss C-Kermit, and the remote + terminal or emulator you are using to access C-Kermit, and the remote host to which C-Kermit is connected. The "semitransparent" qualifier is because of character-set translation as well as several actions taken by the emulator in response to the characters or strings that pass @@ -5953,7 +5953,7 @@ SET HOST /PTY {sh -c "grep somestring *.txt"} printing, also called Controller printing (as distinct from Autoprint or line or screen print). It is intended mainly for use on UNIX workstation consoles (as opposed to remote logins), but with some care - can also be used when accesssing C-Kermit remotely. + can also be used when accessing C-Kermit remotely. Transparent printing is related to APC by sharing C-Kermit's built-in ANSI escape-sequence parser to detect "printer on" and "printer off" @@ -6010,7 +6010,7 @@ SET HOST /PTY {sh -c "grep somestring *.txt"} 2. Only the 7-bit forms of the escape sequences are supported. The 8-bit CSI C1 control is not recognized. 3. Autoprint is not supported, since this requires a full-fledged - terminal emulator with direct accesss to the screen. + terminal emulator with direct access to the screen. 4. The start-print and stop-print sequences pass through to the screen (there is no way to avoid this without causing unacceptable delays or deadlocks in CONNECT mode). Thus if your terminal or emulator @@ -6615,8 +6615,8 @@ SET HOST /PTY {sh -c "grep somestring *.txt"} 4.2.1.3. SECURITY - Some sites might not wish to allow accesss to system commands or - external programs from within Kermit. Such accesss, including all the + Some sites might not wish to allow access to system commands or + external programs from within Kermit. Such access, including all the features described here, can be disabled in various ways: 1. When building from source code, include -DNOPUSH among the CFLAGS. @@ -7480,7 +7480,7 @@ SET HOST /PTY {sh -c "grep somestring *.txt"} mailed or printed and then deleted. This has the advantages of (a) not requiring a temporary file, and (b) allowing mail to have a proper subject in place of the filename. Temporary files were bad not only - because they required (a) space, and (b) writeability of the current + because they required (a) space, and (b) writability of the current directory, but also because using them could result in wiping out an existing file. See [467]Section 4.7 for more about SEND /MAIL and SEND /PRINT. @@ -7791,10 +7791,10 @@ SET HOST /PTY {sh -c "grep somestring *.txt"} 4.4. File Permissions "Permissions" refers to a code associated with a file that specifies - who is allowed to accesss it, and in what manner. For example, the + who is allowed to access it, and in what manner. For example, the owner, the members of one or more groups, the system administrator, and everybody else, might be allowed various combinations of Read, Write, - Append, Execute, or Listing accesss. + Append, Execute, or Listing access. The permission code goes by different names on different platforms. In UNIX, it might be called the filemode. In VMS, it is called the file @@ -7879,7 +7879,7 @@ SET HOST /PTY {sh -c "grep somestring *.txt"} 4.4.2.1.1. UNIX UNIX supports three categories of users, File Owner, Group, and World, - and three types of file accesss permission: Read, Write, and Execute. + and three types of file access permission: Read, Write, and Execute. Thus, a UNIX file's permissions are expressed in 9 bits. The system-dependent permission string for UNIX is a 3-digit octal @@ -7891,7 +7891,7 @@ SET HOST /PTY {sh -c "grep somestring *.txt"} 4.4.2.1.2. VMS VMS supports four categories of users, System, File Owner, Group, and - World, and four types of file accesss permission: Read, Write, Execute, + World, and four types of file access permission: Read, Write, Execute, and Delete. Thus, a VMS file's permissions are expressed in 16 bits. The system-dependent protection string for VMS is a 4-digit hexadecimal @@ -7961,7 +7961,7 @@ SET HOST /PTY {sh -c "grep somestring *.txt"} whether the file "foo" exists; and it runs an inferior process, which might be a problem in some environments for resource and/or security reasons, and won't work at all in a "nopush" environment (e.g. one in - which C-Kermit is configured to forbid accesss to exterior commands and + which C-Kermit is configured to forbid access to exterior commands and programs, e.g. in a VMS "captive account"). In C-Kermit 7.0 on VMS and UNIX, and in K95 1.1.19 and later, the @@ -8154,7 +8154,7 @@ SET HOST /PTY {sh -c "grep somestring *.txt"} shows the "/tmp/foo" file. If you want to see all "foo" files in the /tmp tree, do "cd /tmp" and then "dir /recursive foo". * If a file size of -1 is shown, or date-time of 0000-00-00 00:00:00, - this means the file was located, but accesss to information about + this means the file was located, but access to information about the file was denied to C-Kermit. * In VMS, if FOO.DIR;1 is a directory within your current directory, "directory foo" and "directory [.foo]" list the files in the [.FOO] @@ -8184,7 +8184,7 @@ SET HOST /PTY {sh -c "grep somestring *.txt"} wd /headings *.txt - Of course you can still accesss your external directory listing program + Of course you can still access your external directory listing program by using RUN or "!", e.g. in VMS: run directory /size/date/protection/except=*.obj oofa.*;0 @@ -8597,7 +8597,7 @@ SET HOST /PTY {sh -c "grep somestring *.txt"} /DOTFILES (UNIX and OS-9 only) Normally files whose names begin with "." - are skipped when matching wildcards that do not also beging with + are skipped when matching wildcards that do not also begin with ".". Include /DOTFILES to force these files to be included too. /RECURSIVE @@ -9907,8 +9907,8 @@ SET HOST /PTY {sh -c "grep somestring *.txt"} Chooses buffered file output; this is the default. UNIX does its normal sort of disk buffering. The optional size specifies Kermit's own file output buffer size, and therefore the - frequency of disk accessses (write() system calls) -- the bigger - the size, the fewer the disk accessses. + frequency of disk accesses (write() system calls) -- the bigger + the size, the fewer the disk accesses. SET FILE OUTPUT UNBUFFERED [ size ] This forces each file output write() call to actually commit the @@ -10548,7 +10548,7 @@ SET HOST /PTY {sh -c "grep somestring *.txt"} 4.20.2.5. Streaming on X.25 Connections - We have only limited accesss to X.25 networks. One trial was performed + We have only limited access to X.25 networks. One trial was performed in which the 1MB Solaris 2.4 Sparc executable was transferred over a SunLink X.25 connection; nothing is known about the actual physical connection. With a packet length of 8000 and a window size of 30, the @@ -10901,8 +10901,8 @@ SET HOST /PTY {sh -c "grep somestring *.txt"} visual aspect of the packet that would be seen by the terminal (or, more to the point, the emulator, such as K95). This way, only C-Kermit goes into RECEIVE mode, and not also the terminal emulator through - which C-Kermit is accesssed. And therefore, it is no longer necessary - to SET TERMINAL AUTODOWNLOAD OFF to prevent multiple Kermits from going + which C-Kermit is accessed. And therefore, it is no longer necessary to + SET TERMINAL AUTODOWNLOAD OFF to prevent multiple Kermits from going into receive mode at once, but of course it is still necessary to ensure that, when you have multiple Kermits in a chain, that the desired one receives the autodownload. @@ -10949,7 +10949,7 @@ SET HOST /PTY {sh -c "grep somestring *.txt"} started in interactive mode, and would cause it to exit if it entered server mode via command-line option.) When C-Kermit is to be the server, you can use { ENABLE, DISABLE } EXIT to - control the client's accesss to this feature. + control the client's access to this feature. REMOTE MKDIR directory-name Tells the client to ask the server to create a directory with @@ -11119,8 +11119,8 @@ SET HOST /PTY {sh -c "grep somestring *.txt"} When attempting to execute a REMOTE RMDIR, the server can remove only a single directory, not an entire sequence or tree. The system service that is called to remove the directory generally requires not only that - the server process has write delete accesss, but also that the - directory contain no files. + the server process has write delete access, but also that the directory + contain no files. In the future, a REMOTE RMDIR /RECURSIVE command (and the accompanying protocol) might be added. For now, use the equivalent REMOTE HOST @@ -11389,7 +11389,7 @@ C-Kermit> remote directory | sort +0.22 -0.40 CP855 This PC Code Page contains all the Cyrillic letters that are also in ISO 8859-5, and is therefore useful for non-Russian - Cyrillic text (Ukrainian, Belorussian, etc), unlike CP866, which + Cyrillic text (Ukrainian, Belarusian, etc), unlike CP866, which has a smaller repertoire of Cyrillic letters. CP1251 @@ -11530,7 +11530,7 @@ C-Kermit> remote directory | sort +0.22 -0.40 [547]http://www.unicode.org/ - and accesss the various online introductions, FAQs, technical reports, + and access the various online introductions, FAQs, technical reports, and other information. For greater depth, order the latest version of the published Unicode Standard. The following overview contains a great many oversimplifications and perhaps an opinion or two. @@ -11598,7 +11598,7 @@ C-Kermit> remote directory | sort +0.22 -0.40 bytes in UCS-2 text pose problems for current applications and transmission methods. And to make matters worse, different hardware platforms store UCS-2 characters in different byte order. Thus a UCS-2 - file transferred by FTP (or accesssed via NFS, etc) between two + file transferred by FTP (or accessed via NFS, etc) between two computers with different architecture might have its bytes in the wrong order (or worse; see [549]Section 6.6.5.1 ). @@ -11676,7 +11676,7 @@ C-Kermit> remote directory | sort +0.22 -0.40 storage. Any officially sanctioned method of doing this is called a UCS Transformation Format, or UTF. One such method, called UTF-16, is essentially identical with UCS-2 except that it designates certain code - values as "escape sequences" (called surrogate pairs) to accesss + values as "escape sequences" (called surrogate pairs) to access characters in other planes without having to use full UCS-4. We won't discuss UTF-16 further here, since at the moment there are no other planes. Several other UTF's (such as UTF-1, UTF-2, and UTF-7) have @@ -11691,7 +11691,7 @@ C-Kermit> remote directory | sort +0.22 -0.40 conversion between ASCII and UTF-8 is no conversion at all, and applications or platforms (such as Plan 9 from Bell Labs) that use UTF-8 "for everything" can still run traditional ASCII-only - applications and be accesssed from them. In particular, unlike UCS-2, + applications and be accessed from them. In particular, unlike UCS-2, ASCII characters are not padded with NUL bytes. But also unlike UCS-2, there is no transparency for Latin-1 or any other non-ASCII character set. Every non-ASCII UCS-2 character is represented by a sequence of 2 @@ -12092,7 +12092,7 @@ C-Kermit> remote directory | sort +0.22 -0.40 UTF-8 was first used in Plan 9 and soon will be available in Linux. It will probably spread from there (Unicode in some form is, of course, - also used in Windows NT, but only internally -- not for accesss from + also used in Windows NT, but only internally -- not for access from outside). To use UTF-8 or any other character set that uses 8-bit bytes in your @@ -12137,7 +12137,7 @@ C-Kermit> remote directory | sort +0.22 -0.40 stated without doubt that C-Kermit's key mapping will not work for UTF-8 values, since (a) the key map is indexed by 8-bit byte values and (b) C-Kermit reads keystrokes a byte at a time (these comments do not - apply to K95, which has direct accesss to the keyboard and can read + apply to K95, which has direct access to the keyboard and can read "wide" keycodes and uses them to index a "wide" keymap). Restrictions: As noted, the CONNECT command does not support UCS-2 as a @@ -13236,7 +13236,7 @@ while true { IF WRITEABLE name Succeeds if name is the name of an existing file or directory - that is writeable, e.g.: + that is writable, e.g.: if not writeable \v(lockdir) echo Please read installation instructions! @@ -13319,7 +13319,7 @@ while true { [a b c d e f g h i j k l m n o p q r s t u v w x y z] Note that \%* can not be used at top level, since Kermit does not have - accesss to the raw command line (only to its elements separately, after + access to the raw command line (only to its elements separately, after they have been processed by the shell and the C library). C-Kermit 7.0 also adds a SHIFT command: @@ -13974,11 +13974,31 @@ while true { creating \&b[] if necessary or, if \&b[] is already declared, stopping early if its size is less than 14. - ARRAY COPY \&a[17] \&b + ARRAY COPY \&a[17:] \&b This copies all the elements of \&a[] starting with 17 until the last to \&b[], creating \&b[] if necessary or, if \&b[] is already declared, stopping early if \&b[] is - not big enough. + not big enough. Suppose, for example, you have a script + whose arguments are string1, string2, and a list of files, + whose job is to change all occurrences of string1 to + string2 in each of the files. But if the list of files is + omitted, then "*" (all files in the current directory) is + assumed: + +if < \v(argc) 3 exit 1 "Usage: \%0 string1 string2 [ files ]" +if not def \%3 { + .n := \ffiles(*,&a) +} else { + array copy &_[3:] &a + .n := \fdim(&a) +} +for i 1 n 1 { + ! cat \&a[i] | sed -e "s|\%1|\%2|g" > /tmp/_x + rename /tmp/_x \&a[i] +} + + ARRAY COPY \&a[17] \&b + Same as previous example. ARRAY CLEAR arrayname Sets all the elements of the array to the empty value. You may @@ -14142,10 +14162,10 @@ while true { * An attempt to set the value of an array element that is out of bounds or that has not been declared simply fails. - C programmers expect an array of size nto have elements 0 through n-1. + C programmers expect an array of size n to have elements 0 through n-1. Fortran programmers expect the same array to have elements 1 through n. C-Kermit accommodates both styles; when you declare an array of size n, - it has n=1 elements, 0 through n, and you can use the array in your + it has n+1 elements, 0 through n, and you can use the array in your accustomed manner, 0-based or 1-based. However, note that C-Kermit has certain biases towards 1-based arrays: @@ -14383,7 +14403,7 @@ while true { "file:index", or "file.index", and the code above would have worked just as well (with the corresponding syntax adjustments). But to be able to use an associative array in a program after the array is built, - we need a method of accesssing all its elements without knowing in + we need a method of accessing all its elements without knowing in advance what they are. That's where the chosen notation comes in. First of all, any macro name that ends with "" (where "xxx" is any @@ -14427,7 +14447,7 @@ while true { .max := \&b[\%i] } } - echo Most popular file: \m(name), accessses: \m(max) + echo Most popular file: \m(name), accesses: \m(max) This lists the files and counts and then announces which file has the highest count. @@ -14871,7 +14891,7 @@ while true { contain the command-line arguments, if any, that appear after "--" or "=", if any. This array is saved and restored around macro calls; recall that inside macros it contains the macro argument vector - (allowing you to accesss arguments programmatically, and to have more + (allowing you to access arguments programmatically, and to have more than 9 of them). At top level, notice the difference between the \&@[] and \&_[] arrays. @@ -15046,7 +15066,7 @@ while true { shell. In VMS and other non-UNIX platforms, the Kerbang line has no effect and can be omitted. - It might be desireable for a script to know whether it has been invoked + It might be desirable for a script to know whether it has been invoked directly from the shell (as a Kerbang script) or by a TAKE command given to the Kermit prompt or in a Kermit command file or macro. This can be done as in this example: @@ -15330,11 +15350,13 @@ ELSE command-list the rules of precedence. All Boolean assertions are always evaluated; there is no "early stopping" property and therefore no question about when or if side effects will occur -- if any Boolean - assertion has side effects, they will always occur. + assertion has side effects, they will always occur. (Early stopping + is, however, possible with the [631]S-Expression IF introduced in + C-Kermit 8.0.) Constructions of arbitrary complexity are possible, within reason. - Also see [631]Section 7.4 for new IF / WHILE conditions. + Also see [632]Section 7.4 for new IF / WHILE conditions. 7.21. Screen Formatting and Cursor Control @@ -15502,6 +15524,10 @@ ELSE command-list 7.23. Floating-Point Arithmetic + For a more convenient way of dealing with floating-point numbers + than the one described here, see the [633]C-Kermit 8.0 update notes, + the section on [634]S-Expressions. + C-Kermit 7.0 adds limited support for floating-point numbers (numbers that have fractional parts, like 3.141592653). This support is provided through a small repertoire of functions and in Boolean expressions that @@ -15693,7 +15719,7 @@ ELSE command-list result to \ffpround(xxx,0) (to round). Floating-point numbers (or variables or functions that return them) can - be used in Boolean expressions (see [632]Section 7.20.2) that compare + be used in Boolean expressions (see [635]Section 7.20.2) that compare numbers: = x y @@ -15724,7 +15750,7 @@ ELSE command-list and is executed otherwise. Floating-point numbers can be sorted using ARRAY SORT /NUMERIC (see - [633]Section 7.10.5 ). + [636]Section 7.10.5 ). Two floating-point constants are provided: @@ -15867,7 +15893,7 @@ ELSE command-list Syntactically, \m(name) and \s(name) differ only in that the sequence [*] at the end of the name (where * is any sequence of 0 or more characters) is treated as substring notation in \s(name), but is - considered part of the name in \m(name) (to see why, see [634]Section + considered part of the name in \m(name) (to see why, see [637]Section 7.10.9). 7.26. New WAIT Command Options @@ -15936,7 +15962,7 @@ ELSE command-list heading is the time of the most recent event (including when the program started). - See [635]Section 1.10, where the \v(kbchar) variable is explained. This + See [638]Section 1.10, where the \v(kbchar) variable is explained. This lets you modify a loop like the one above to also accept single-character commands, which interrupt the WAIT, and dispatch accordingly. For example: @@ -15978,8 +16004,8 @@ ELSE command-list 8. USING OTHER FILE TRANSFER PROTOCOLS In C-Kermit 7.0, alternative protocols can be selected using switches. - Switches are described in [636]Section 1.5; the use of - protocol-selection switches is described in [637]Section 4.7.1. + Switches are described in [639]Section 1.5; the use of + protocol-selection switches is described in [640]Section 4.7.1. Example: send /binary /protocol:zmodem x.tar.gz @@ -16025,7 +16051,7 @@ ELSE command-list where a keyword (rather than a single letter) specifies the function, and if an argument is to be included, it is separated by a colon (or equal sign). Most of the new extended-format command-line options are - only for use with the Internet Kermit Service Daemon; see the [638]IKSD + only for use with the Internet Kermit Service Daemon; see the [641]IKSD Administration Guide for details. However, several of them are also general in nature: @@ -16150,7 +16176,7 @@ ELSE command-list become the name of the script file, rather than the pathname of the C-Kermit program, which is its normal value. Primarily for use in the top line of "Kerbang" scripts in UNIX (see - [639]Section 7.19). Example from UNIX command line: + [642]Section 7.19). Example from UNIX command line: $ kermit [ regular kermit args ] + filename @@ -16190,11 +16216,11 @@ ELSE command-list kermit -L -s "*.c" In UNIX only, "kermit -L -s ." means to send the current - directory tree. See [640]Sections 4.10 and [641]4.11 about + directory tree. See [643]Sections 4.10 and [644]4.11 about recursive file transfer. -V - Equivalent to SET FILE PATTERNS OFF ([642]Section 4.3) and SET + Equivalent to SET FILE PATTERNS OFF ([645]Section 4.3) and SET TRANSFER MODE MANUAL. In other words, take the FILE TYPE setting literally. For example, "kermit -VT oofa.bin" means send the file in Text mode, no matter what its name is and no matter @@ -16226,7 +16252,7 @@ ELSE command-list thus it is called G-Kermit (for GNU Kermit). All it does is send and receive files, period. You can find it at: - [643]http://www.columbia.edu/kermit/gkermit.html + [646]http://www.columbia.edu/kermit/gkermit.html Where the C-Kermit 7.0 binary might be anywhere from 1 to 3 million bytes in size, the G-Kermit binary ranges from 30K to 100K, depending @@ -16245,7 +16271,7 @@ ELSE command-list In such cases G-Kermit might be preferred since it generally starts up faster, and yet transfers files just as fast on most (but not necessarily all) kinds of connections; for example, it supports - streaming ([644]Section 4.20). + streaming ([647]Section 4.20). G-Kermit is also handy for bootstrapping. It is easier to load on a new computer than C-Kermit -- it fits on a floppy diskette with plenty of @@ -16255,7 +16281,7 @@ ELSE command-list diskette on Xenix with "dosread", and then use G-Kermit to receive C-Kermit (which does not fit on a diskette). If diskettes aren't an option, other bootstrapping methods are possible too -- see the - [645]G-Kermit web page for details. + [648]G-Kermit web page for details. III. APPENDICES @@ -16632,7 +16658,7 @@ CC Nation Effective Mandatory Notes IV. ERRATA & CORRIGENDA - The following errors in [646]Using C-Kermit, Second Edition, first + The following errors in [649]Using C-Kermit, Second Edition, first printing, have been noted. First, some missing acknowledgements for C-Kermit 6.0: JE Jones of @@ -16700,7 +16726,7 @@ COVER "COS" is a misprint. There is no COS. Pretend it says "SCO" or "VOS". 393 \Fverify() description. The 3rd sentence could be stated more clearly as "If all characters in string2 are also in string1, 0 is returned." 398 Copying \ffiles() results to an array before is not required as of - C-Kermit 7.0 (see [647]Section 7.3). + C-Kermit 7.0 (see [650]Section 7.3). 403 In "(\%a + 3) * (\%b 5)", a minus sign is missing between b and 5. 407 C-Kermit 7.0 no longer supports multiline GET. Change "get, \%1, \%2" to "get {\%1} {\%2}" or "get /as:{\%2} {\%1}". @@ -16721,7 +16747,7 @@ COVER "COS" is a misprint. There is no COS. Pretend it says "SCO" or "VOS". 440 Change "set terminal byteszie" to "set terminal bytesize". Change "input Password:" to "input 10 Password". -448 Franchise script: "accesss line" should be "accesss \m(line)". +448 Franchise script: "access line" should be "access \m(line)". 453 There are two incorrectly coded IF statements in the DELIVER macro definition. Replace both occurrences of "if > \%1 \%3 {" with "xif > \%i \%3 {" (replace "if" by "xif" and "\%1" with "\%i"). @@ -16810,7 +16836,7 @@ Index: Missing entries: SET { SEND, RECEIVE } PATHNAMES, Call waiting, ... suggestions for improvements, additional index entries, and any other comments: - [648]kermit@columbia.edu + [651]kermit@columbia.edu APPENDIX V. ADDITIONAL COPYRIGHT NOTICES @@ -17000,11 +17026,11 @@ APPENDIX V. ADDITIONAL COPYRIGHT NOTICES Used for Big Number library in Kermit 95 (k95crypt.dll, k2crypt.dll). - [ [649]Top ] [ [650]C-Kermit ] [ [651]Kermit Home ] - __________________________________________________________________ + [ [652]Top ] [ [653]C-Kermit ] [ [654]Kermit Home ] __________________________________________________________________ - CKERMIT70.HTM / The Kermit Project / Columbia University / 8 Feb 2000 + CKERMIT70.HTM / The Kermit Project / Columbia University / 8 Feb 2000 / + Last update: 8 Aug 2011 References @@ -17638,24 +17664,27 @@ References 628. http://www.columbia.edu/kermit/ckermit70.html#x7.5 629. http://www.columbia.edu/kermit/ckb2.htm 630. http://www.columbia.edu/kermit/ckermit80.html - 631. http://www.columbia.edu/kermit/ckermit70.html#x7.4 - 632. http://www.columbia.edu/kermit/ckermit70.html#x7.20.2 - 633. http://www.columbia.edu/kermit/ckermit70.html#x7.10.5 - 634. http://www.columbia.edu/kermit/ckermit70.html#x7.10.9 - 635. http://www.columbia.edu/kermit/ckermit70.html#x1.10 - 636. http://www.columbia.edu/kermit/ckermit70.html#x1.5 - 637. http://www.columbia.edu/kermit/ckermit70.html#x4.7.1 - 638. http://www.columbia.edu/kermit/iksd.html - 639. http://www.columbia.edu/kermit/ckermit70.html#x7.19 - 640. http://www.columbia.edu/kermit/ckermit70.html#x4.10 - 641. http://www.columbia.edu/kermit/ckermit70.html#x4.11 - 642. http://www.columbia.edu/kermit/ckermit70.html#x4.3 - 643. http://www.columbia.edu/kermit/gkermit.html - 644. http://www.columbia.edu/kermit/ckermit70.html#x4.20 - 645. http://www.columbia.edu/kermit/gkermit.html - 646. http://www.columbia.edu/kermit/ckb2.htm - 647. http://www.columbia.edu/kermit/ckermit70.html#x7.3 - 648. mailto:kermit@columbia.edu - 649. http://www.columbia.edu/kermit/ckermit70.html#top - 650. http://www.columbia.edu/kermit/ckermit.html - 651. http://www.columbia.edu/kermit/index.html + 631. http://www.columbia.edu/kermit/ckermit80.html#x9 + 632. http://www.columbia.edu/kermit/ckermit70.html#x7.4 + 633. http://www.columbia.edu/kermit/ckermit80.html + 634. http://www.columbia.edu/kermit/ckermit80.html#x9 + 635. http://www.columbia.edu/kermit/ckermit70.html#x7.20.2 + 636. http://www.columbia.edu/kermit/ckermit70.html#x7.10.5 + 637. http://www.columbia.edu/kermit/ckermit70.html#x7.10.9 + 638. http://www.columbia.edu/kermit/ckermit70.html#x1.10 + 639. http://www.columbia.edu/kermit/ckermit70.html#x1.5 + 640. http://www.columbia.edu/kermit/ckermit70.html#x4.7.1 + 641. http://www.columbia.edu/kermit/iksd.html + 642. http://www.columbia.edu/kermit/ckermit70.html#x7.19 + 643. http://www.columbia.edu/kermit/ckermit70.html#x4.10 + 644. http://www.columbia.edu/kermit/ckermit70.html#x4.11 + 645. http://www.columbia.edu/kermit/ckermit70.html#x4.3 + 646. http://www.columbia.edu/kermit/gkermit.html + 647. http://www.columbia.edu/kermit/ckermit70.html#x4.20 + 648. http://www.columbia.edu/kermit/gkermit.html + 649. http://www.columbia.edu/kermit/ckb2.htm + 650. http://www.columbia.edu/kermit/ckermit70.html#x7.3 + 651. mailto:kermit@columbia.edu + 652. http://www.columbia.edu/kermit/ckermit70.html#top + 653. http://www.columbia.edu/kermit/ckermit.html + 654. http://www.columbia.edu/kermit/index.html diff --git a/ckermit80.txt b/ckermit80.txt index 7aae91a..196b68b 100644 --- a/ckermit80.txt +++ b/ckermit80.txt @@ -385,7 +385,7 @@ CONTENTS 1858. + General: o "Closing blah..." message upon exit could not be - surpressed. + suppressed. o Added /PAGE and /NOPAGE to DELETE switches. o Added GO response for DELETE /ASK (delete all the rest without asking). @@ -498,7 +498,7 @@ CONTENTS + We now make every attempt to not write passwords to the debug.log. + New Certificate Authority certificates file, includes the - Kermit Project at Columbia University so you can accesss our + Kermit Project at Columbia University so you can access our IKSD securely. + Secure targets improved and better documented in Unix makefile. @@ -1116,7 +1116,7 @@ set host /pipe ssh -e none -l olga -T -s hq.xyzcorp.com kermit PUT), they apply only to that command. /USER:name - To be used in case a page requires a username for accesss. The + To be used in case a page requires a username for access. The username is sent with page requests. If it is given with the OPEN command it is saved until needed. If a username is included in a URL, it overrides the username given in the switch. @@ -1127,7 +1127,7 @@ set host /pipe ssh -e none -l olga -T -s hq.xyzcorp.com kermit performed securely on HTTPS connections. /PASSWORD:text - To be used in case a web page requires a password for accesss. + To be used in case a web page requires a password for access. The password is sent with page requests. If it is given with the OPEN command it is saved until needed. If a password is given in a URL, it overrides the one given here. CAUTION: (same as for @@ -1540,7 +1540,7 @@ set host /pipe ssh -e none -l olga -T -s hq.xyzcorp.com kermit http www.columbia.edu -g kermit/index.html - If you need to accesss a website for which a username and password are + If you need to access a website for which a username and password are required, you can supply them on the command line with -u and -P. If you include a username but omit the password, Kermit prompts you for it: @@ -2034,7 +2034,7 @@ set host /pipe ssh -e none -l olga -T -s hq.xyzcorp.com kermit the server does support accounts, the account is accepted if it is valid and rejected if it is not. The account might be used for charging purposes or it might be a secondary password, or it - might be used for any other purpose, such as an accesss password + might be used for any other purpose, such as an access password for a particular disk. Servers that support accounts might or might not allow or require the account to be sent prior to login; usually it is sent after login, if at all. Synonym: @@ -2122,6 +2122,34 @@ bye ; Log out and disconnect [ [240]Top ] [ [241]FTP Top ] [ [242]C-Kermit Home ] [ [243]Kermit Home ] +3.1.5. Making Proxy Connections + + The simplist form of firewall traversal is the HTTP CONNECT command. + The CONNECT command was implemented to allow a public web server which + usually resides on the boundary between the public and private networks + to forward HTTP requests from clients on the private network to public + web sites. In order to allow secure web connections to be established, + the CONNECT command works by authenticating the client with a + username/password and then establishing a tunnel to the desired host. + + Many web servers support the CONNECT command and it can be configured + to allow outgoing connections to authenticated user to any TCP/IP + hostname/port combination accessible to the web server. The limitations + of HTTP CONNECT is that it can only be used for outgoing connections + for protocols that are implemented using TCP/IP. Protocols such as + Kerberos authentication that use UDP/IP cannot be tunneled using HTTP + CONNECT. + + Kermit provides support for the use of HTTP CONNECT proxy services with + the command: + + SET TCP HTTP-PROXY [/USER:username /PASSWORD:password] hostname/ip-address[:po +rt] + + When a port is not specified the default port configured on the HTTP + server is used. This is frequently port 443. When a hostname is + specified, it is resolved using the DNS available to the web server. + 3.2. Making Secure FTP Connections Also see: [244]Accessing IBM Information Exchange with Kermit. @@ -2129,8 +2157,8 @@ bye ; Log out and disconnect In the previous section, you can see several examples of traditional insecure authentication: username and password sent across the network in clear text. Of course this is bad practice on at least two counts: - (1) storing passwords in files (such as script files) gives accesss to - the target systems to anybody who can obtain read accesss to your + (1) storing passwords in files (such as script files) gives access to + the target systems to anybody who can obtain read access to your scripts; and (2) sending this information over the network leaves it open to interception by network sniffers or compromised hosts. @@ -2138,7 +2166,7 @@ bye ; Log out and disconnect servers are beginning to appear that offer secure forms of authentication, in which no information is sent over the network that would allow anyone who intercepts it to usurp your identity and gain - your accesss rights. + your access rights. Kermit provides an equivalent form of FTP security for each type of IETF standard security implemented in Telnet. These include @@ -2193,7 +2221,7 @@ bye ; Log out and disconnect SET FTP CREDENTIAL-FORWARDING { ON, OFF } Tells whether end-user credentials are to be forwarded to the server if supported by the authentication method (GSSAPI-KRB5 - only). This is often required to allow accesss to distributed + only). This is often required to allow access to distributed file systems (e.g. AFS.) SET FTP DATA-PROTECTION-LEVEL { CLEAR, CONFIDENTIAL, PRIVATE, SAFE } @@ -2344,7 +2372,7 @@ bye ; Log out and disconnect SET QUIET { ON, OFF } This command applies to Kermit in general, not just FTP. OFF by - default; when ON, it surpresses most messages from most commands + default; when ON, it suppresses most messages from most commands as well as the file-transfer display. SET FTP PROGRESS-MESSAGES { ON, OFF } @@ -2425,7 +2453,7 @@ bye ; Log out and disconnect transfer immediately and fail if an error occurs with any single file in the group. Example: you have given Kermit a list of files to send, and one of the files can not be found, or read - permission is denied. Note that cancelling a file by typing 'X' + permission is denied. Note that canceling a file by typing 'X' during transfer is not considered an error (if you want to cancel the entire transfer, type 'Z' or Ctrl-C). @@ -2688,7 +2716,7 @@ bye ; Log out and disconnect When used with FTP DELETE, the /RECURSIVE switch deletes files but not directories, and furthermore depends on the server providing recursive file lists, which is not the normal - behavior. For further details, see the decriptions of these + behavior. For further details, see the descriptions of these switches in [274]Section 3.6. Synonyms: FTP MDELETE (Kermit makes no distinction between DELETE and MDELETE); RDELETE. @@ -2784,7 +2812,7 @@ bye ; Log out and disconnect directory to the server's /tmp directory. This works only if the server uses the same directory notation that you used in the as-name AND the given directory already exists on the server AND if you have write - accesss to it. + access to it. Use caution when uploading from a case-sensitive file system, such as UNIX, to a file system that is not case sensitive, such as Windows or @@ -2886,7 +2914,7 @@ C-Kermit>ftp put ? Filename, or switch, one of the following: plus all directories beneath it, including empty directories, replicating the directory structure on the server. No special capabilities are required in the server, but of course your - login ID on the server must have the appropriate accesss and + login ID on the server must have the appropriate access and permission to create directories. Recursive PUTs work not only between like platforms (e.g. UNIX to UNIX) but also between unlike ones (e.g. UNIX to VMS or Windows), in which case @@ -2987,7 +3015,7 @@ C-Kermit>ftp put ? Filename, or switch, one of the following: Tells Kermit to ask the server to rename each file according to the given template as soon as, and only if, it has been received completely and successfully. The template works as in /AS-NAME. - Requires write and rename accesss on the server, so doesn't + Requires write and rename access on the server, so doesn't usually work with (e.g.) anonymous uploads to public incoming areas where the permissions don't allow renaming. Examples: @@ -3480,7 +3508,7 @@ C-Kermit>ftp put ? Filename, or switch, one of the following: /DELETE Each file that is downloaded successfully is to be deleted from - the server. Requires the appropriate file accesss rights on the + the server. Requires the appropriate file access rights on the server. /SERVER-RENAME-TO:template @@ -3964,18 +3992,18 @@ C-Kermit>ftp put ? Filename, or switch, one of the following: REMOTE TYPE (RTYPE) FTP TYPE REMOTE EXIT (REXIT) FTP BYE - The commands in the right-hand column always accesss FTP. The commands - in the left column can accesss either Kermit protocol or FTP: + The commands in the right-hand column always access FTP. The commands + in the left column can access either Kermit protocol or FTP: * When GET-PUT-REMOTE is set to KERMIT, or to AUTO when there is no - FTP connection, the commands in the left-hand column accesss Kermit + FTP connection, the commands in the left-hand column access Kermit protocol, and those right-hand column are required for FTP. * When GET-PUT-REMOTE is set to FTP, or to AUTO when there is an - active FTP connection, the commands in the left-hand column accesss - the FTP connection and can not be used to accesss Kermit protocol. + active FTP connection, the commands in the left-hand column access + the FTP connection and can not be used to access Kermit protocol. In this case, if you want to be able to use both Kermit protocol and the FTP connection, you must SET GET-PUT-REMOTE KERMIT, and - then use the FTP commands in the right-hand column to accesss the + then use the FTP commands in the right-hand column to access the FTP connection. Note that file-management commands such as DIRECTORY, DELETE, CD, PWD, @@ -4354,12 +4382,12 @@ C-Kermit>ftp put ? Filename, or switch, one of the following: FTP SIZE filename Sends a SIZE directive to the server for the given file. The filename must not contain wildcards. The server responds with an - error if the file can't be found, is not accesssible, or the - SIZE directive is not supported, otherwise with the length of - the file in bytes, which Kermit displays and also makes - available to you in its \v(ftp_message) variable. If the - directive is successful, Kermit (re-)enables it for internal use - by the GET and MGET directives on this connection. + error if the file can't be found, is not accessible, or the SIZE + directive is not supported, otherwise with the length of the + file in bytes, which Kermit displays and also makes available to + you in its \v(ftp_message) variable. If the directive is + successful, Kermit (re-)enables it for internal use by the GET + and MGET directives on this connection. FTP MODTIME filename Works just like the SIZE directive except it sends an MDTM @@ -5213,7 +5241,7 @@ mget /nlst t[1234].h 6.6. Arrow Keys - As of version 8.0.201, C-Kermit on most platforms lets you accesss the + As of version 8.0.201, C-Kermit on most platforms lets you access the command history buffer with arrow keys, just as you always could with control characters. The restrictions are: @@ -5224,7 +5252,7 @@ mget /nlst t[1234].h This change was made to facilitate command recall in Linux-based PDAs that don't have a Control key, or at least not one that's easily (or - always) accesssible, such as the Sharp Zaurus SL5500. + always) accessible, such as the Sharp Zaurus SL5500. [ [391]Top ] [ [392]Contents ] [ [393]C-Kermit Home ] [ [394]Kermit Home ] @@ -5606,7 +5634,7 @@ mget /nlst t[1234].h SET ROOT directory Like UNIX chroot, without requiring privilege. Sets the root for - file accesss, does not allow reference to or creation of files + file access, does not allow reference to or creation of files outside the root, and can't be undone. SET SEND PERMISSIONS { ON, OFF } @@ -6098,7 +6126,7 @@ ond. The following new or improved built-in functions are available: - \fcmdstack() Allows programmatic accesss to the command stack. + \fcmdstack() Allows programmatic access to the command stack. \fcvtdate() [448]Section 8.13, format options added \fdelta2secs() [449]Section 8.13 \fdostounixpath(s1) Converts a DOS filename to Unix format. @@ -6124,7 +6152,7 @@ ond. \fverify(s1,s2,n) As of version 8.0.211, returns -1 if s2 is an empty string. Previously it returned 0, making \fverify(abc,\%a) look as if - \%a was a string combosed of a's, b's, and/or c's when in fact + \%a was a string composed of a's, b's, and/or c's when in fact it contained nothing. \fcode(string) @@ -6302,7 +6330,7 @@ ond. 8.7.3. The \fcmdstack() Function - The new \fcmdstack() function gives accesss to the command stack: + The new \fcmdstack() function gives access to the command stack: \fcmdstack(n1,n2) Arguments: n1 is the command stack level. If omitted, the @@ -7498,7 +7526,7 @@ Position Contents displaying summary results. You can do this by defining a macro named ON_CTRLC. When Ctrl-C is detected, and a macro with this name is defined, Kermit executes it from the current command level, thus giving - it full accesss to the environment in which the interruption occurred, + it full access to the environment in which the interruption occurred, including local variables and open files. Only when the ON_CTRLC macro completes execution is the command stack rolled back to top level. @@ -7867,7 +7895,7 @@ def newarea { ON means always print the value; OFF means never print it. In any case, the value of the most recent S-Expression (and the - S-Expression itself) may be accesssed programmatically through the + S-Expression itself) may be accessed programmatically through the following variables: \v(sexpression) @@ -9284,7 +9312,7 @@ def newarea { Added in C-Kermit 8.0.201: Rudimentary support for Caller ID, for use with the ANSWER command. If the modem reports Caller ID information, - Kermit stores it in variables that you can accesss after the call is + Kermit stores it in variables that you can access after the call is answered: \v(callid_date) The date of the call @@ -9325,7 +9353,7 @@ def newarea { Kermit presently has no built-in knowledge of the Caller ID capabilities or commands of the modems in its database. - Since the variables can be accesssed only after the call is answered, + Since the variables can be accessed only after the call is answered, the only way to refuse a call is to answer it, inspect the variables, and then hang it up if desired. @@ -9476,8 +9504,8 @@ def newarea { 14. DIALOUT FROM TELNET TERMINAL SERVERS For years, C-Kermit has supported dialing out from Telnet modem servers - (also called reverse terminal servers or accesss servers), but until - now there was no way for Kermit to control the communication parameters + (also called reverse terminal servers or access servers), but until now + there was no way for Kermit to control the communication parameters (speed, parity, etc) on the serial port of the terminal server; it had to use whatever was there. @@ -9514,7 +9542,7 @@ def newarea { connection automatically when the telephone call is hung up (e.g. "autohangup" on Cisco models). - For a Linux-based Telnet Com-Port server, click the Srdird link: + For a Linux-based Telnet Com-Port server, click the Sredird link: [ [575]Top ] [ [576]Contents ] [ [577]Sredird ] [ [578]C-Kermit Home ] [ [579]Kermit Home ] diff --git a/ckermit90.txt b/ckermit90.txt index 09f7c8b..adf6ee3 100644 --- a/ckermit90.txt +++ b/ckermit90.txt @@ -13,8 +13,10 @@ C-Kermit 9.0 Update Notes - Note: C-Kermit 9.0.301 contains a correction that applies only to + Note: C-Kermit 9.0.301 contains a correction that applies only to Solaris 10 and 11. + C-Kermit 9.0.302 contains corrections that apply only to FreeBSD 8 + and 9. * [15]Large Files * [16]How to Test Large-File Transfer * [17]Arithmetic with Large Integers @@ -51,21 +53,21 @@ C-Kermit 9.0 Update Notes because it's an interactive program, not a compiler. The scripting language is the command language. Kind of like the Unix shell but "somewhat" less cryptic, including concepts not only from C but from - PL/I, Snobol, LISP, and Smalltalk. The language itself is built upon - the command language of the much-loved [36]DECSYSTEM-20 from the 1970s - and 80s, the Clipper Ship of the Text Era. (Text is not a bad word. - Those of us who can touch-type and who are proficient in text-based - computing environments like Unix shell or VMS DCL are likely to be - orders of magnitude more productive than users of GUIs.) + PL/I, Snobol, LISP, Bliss, and Smalltalk. The language itself is built + upon the command language of the much-loved [36]DECSYSTEM-20 from the + 1970s and 80s, the Clipper Ship of the Text Era. (Text is not a bad + word. Those of us who can touch-type and who are proficient in + text-based computing environments like Unix shell or VMS DCL are likely + to be orders of magnitude more productive than users of GUIs.) Thanks to (at least) Jeff Altman, William Bader, Ian Beckwith, Nelson - Beebe, Gerry Belanger, Joop Boonen, Rob Brown, Christian Corti, John - Dunlap, Peter Eichhorn, Carl Friedberg, Terry Kennedy, Günter Knauf, - Jason Lehr, Arthur Marsh, Lewis McCarthy, Gary Mills, Jonathan Reams, - Mike Rechtman, Mark Sapiro, Steven Schweda (SMS), Kinjal Shah, Michael - Sokolov, Andy Tanenbaum, Seth Theriault, Zach A. Thomas, Martin - Vorländer, and Eric Weaver for assistance, and to Hewlett-Packard - Company for support. + Beebe, Gerry Belanger, Joop Boonen, Rob Brown, Christian Corti, Alexey + Dokuchaev, John Dunlap, Peter Eichhorn, Carl Friedberg, Terry Kennedy, + Günter Knauf, Jason Lehr, Arthur Marsh, Lewis McCarthy, Gary Mills, Ed + Ravin, Jonathan Reams, Mike Rechtman, Mark Sapiro, Steven Schweda + (SMS), Kinjal Shah, Michael Sokolov, Andy Tanenbaum, Seth Theriault, + Zach A. Thomas, Martin Vorländer, and Eric Weaver for assistance, and + to Hewlett-Packard Company for support. - Frank da Cruz [37]fdc@columbia.edu, 30 June 2011 @@ -86,21 +88,23 @@ C-Kermit> send /recursive /dotfiles /nobackup * index.html.~243~). And then I did the same with the FTP sites, about 8GB in all. Watching the file-transfer display was kind of like having 30 years of my life flash before my eyes in a few minutes. Then I - copied the two directories to DVD (the FTP site had to split over 2 + copied the two directories to DVD (the FTP site had to be split over 2 DVDs). The whole operation took under half an hour. The directory tree on the CD is directly usable in Windows, Unix, or any other operating - system (unlike if I had made, say, a gzipped tar archive or a zip + system (unlike if I had transferred the files all in binary mode or all + in text mode, or if I had made, say, a gzipped tar archive or a zip archive). I believe that, to this day, Kermit is the only software that can do this. If someday I have to upload from these DVDs to Unix, VMS, or any other operating system, it can be done exactly the same way, with any necessary conversions on text files done automatically, and - binary files left intact. + binary files left intact, recursively through a whole very large + directory tree. What's New in General Very briefly, the major items: * [39]Open Source license. - * [40]64-bit file accesss and transfer and 64-bit integer arithmetic + * [40]64-bit file access and transfer and 64-bit integer arithmetic on most common platforms. * Support for recent releases of Linux, Mac OS X, *BSD, etc ([41]see table). @@ -132,11 +136,11 @@ Large Files platforms that support them. A "large file" is one whose size is greater than 2^31-1 (2,147,483,647) bytes (2GB-1); that is, one whose size requires more than 31 bits to represent. Before now, Kermit was - able to accesss such files only on 100% 64-bit platforms such as - Digital Unix, later known as Tru64 Unix. In the new release, Kermit - takes advantage of the X/Open Single UNIX Specification Version 2 (UNIX - 98) Large File Support (LFS) specification, which allows 32-bit - platforms to create, accesss, and manage files larger than 2GB. + able to access such files only on 100% 64-bit platforms such as Digital + Unix, later known as Tru64 Unix. In the new release, Kermit takes + advantage of the X/Open Single UNIX Specification Version 2 (UNIX 98) + Large File Support (LFS) specification, which allows 32-bit platforms + to create, access, and manage files larger than 2GB. Accommodating large files required code changes in many modules, affecting not only file transfer, but also file management functions @@ -272,13 +276,12 @@ FORCE-3 Packet Protocol In practice, however, it is possible to code the packet receiver "cheat" by reading the packet data before verifying the block check. - Thus when the receiver is C-Kermit 9.0 Beta.01 or later or E-Kermit 1.7 - or later, it is only necessary to give the "set block 5" command to the + Thus when the receiver is C-Kermit 9.0 or later or E-Kermit 1.7 or + later, it is only necessary to give the "set block 5" command to the file sender, and the receiver will check for a FORCE-3 first packet. If - the receiver does not support this feature, however, the the initial - packet will be be rejected (after several retries) and the file - transfer will not take place. There is no attempt to "back off" to - normal behavior. + the receiver does not support this feature, however, the initial packet + will be be rejected (after several retries) and the file transfer will + not take place. There is no attempt to "back off" to normal behavior. CAPTION: Table 4. Kermit Protocol Packet Block Check Types @@ -319,7 +322,7 @@ Variable Evaluation a single letter, for example \a, \b, etc. The contributed code evaluated these variables recursively, meaning if the definition of a variable contained variable references, then these were resolved when - derefencing the variable, and the process would continue as deep down + dereferencing the variable, and the process would continue as deep down as necessary to resolve the thing fully. This was sometimes handy, but it had one severe drawback: There was no @@ -402,7 +405,7 @@ Variable Evaluation anyway there should never be any harm in evaluating them recursively because their final value is always (or should be) numeric, not some string that might contain backslashes. - * The VARIABLE-EVALUTION setting is on the command stack. Thus you + * The VARIABLE-EVALUATION setting is on the command stack. Thus you can give this command in a macro, command file, or user-defined function without affecting the calling environment. * The new \frecurse() function forces recursive evaluation of its @@ -889,7 +892,7 @@ Other New Features versions that support large files. * User-settable FTP timeout, works on both the data and control connection. - * FTP accesss to ports higher than 16383. + * FTP access to ports higher than 16383. * Built-in FTP client for VMS. This is the [70]same FTP client Unix C-Kermit has had since version 8.0, minimally adapted to VMS by SMS, supporting binary and Stream_LF file transfer only (in other @@ -1105,7 +1108,7 @@ exit 0 them to analyze web logs, see the Weblog script below. * - Lazy IF Conditions: Third, now you can do this: + Lazy IF Conditions: Now you can do this: define foo some number if foo command @@ -1116,9 +1119,9 @@ exit 0 Of course the old way still works too. But watch out because if the variable name is the same as a symbolic IF condition (for example COUNT), it won't do what you expected. (IF COUNT was used for loop - control in early versions of MS-DOS Kermit, before it got true FOR + control in early versions of MS-DOS Kermit, before it got real FOR and WHILE loops; it was added to C-Kermit for compatibility, and it - can't be removed because it could break existing scripts). + can't be removed because that could break existing scripts). * Escape sequences are now stripped from text-mode session logs not only in CONNECT sessions but also in whatever is logged by the INPUT command; described in the [85]next section. @@ -1307,16 +1310,16 @@ Using External File-Transfer Protocols on Secure Connections ckupty.[ch], which are well-proven in terms of portability and of actually working. They are currently used by SET HOST /PTY for making terminal connections to external processes. But these routines are - written on the assumption that the pty is to be accesssed - interactively, and maybe they are setting the fork/pty arrangement up - in such a way that that's not suitable for file transfer. The Pass One - routine is called xttptycmd() in ckutio.c. + written on the assumption that the pty is to be accessed interactively, + and maybe they are setting the fork/pty arrangement up in such a way + that that's not suitable for file transfer. The Pass One routine is + called xttptycmd() in ckutio.c. So in Pass Two I made a second copy of the routine, yttptycmd(), that manages the pty and fork itself, so all the code is in one place and it's simple and understandable. But it still doesn't work for Zmodem downloads. In this routine, I use openpty() to get the pty pair, which - is not portable, so I can have accesss to both the master and slave pty + is not portable, so I can have access to both the master and slave pty file descriptors. This version can be used only a platforms that have openpty(): Linux, Mac OS X, NetBSD, etc. diff --git a/ckubwr.txt b/ckubwr.txt index 44177a5..38b064a 100644 --- a/ckubwr.txt +++ b/ckubwr.txt @@ -10,8 +10,8 @@ C-Kermit Unix Hints and Tips Frank da Cruz [11]The Kermit Project, [12]Columbia University - As of: C-Kermit 9.0.300 30 June 2011 - This page last updated: Wed Jul 6 10:02:34 2011 (New York USA Time) + As of: C-Kermit 9.0.302, 20 August 2011 + This page last updated: Sun Aug 21 12:08:52 2011 (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 @@ -26,41 +26,44 @@ Known problems with C-Kermit 9.0 * Domain name resolution does not work in Solaris 10 or 11 (fixed in [14]9.0.301). + * UUCP lockfile failure in FreeBSD 8 (fixed in [15]9.0.302). + * Build failure FreeBSD 9 (fixed in [16]9.0.302). * Opening new SSH sessions after closing previous ones sometimes fails. + * Heimdal Kerberos not supported. - [ [15]C-Kermit ] [ [16]Installation Instructions ] [ [17]TUTORIAL ] + [ [17]C-Kermit ] [ [18]Installation Instructions ] [ [19]TUTORIAL ] CONTENTS - 1. [18]INTRODUCTION - 2. [19]PREBUILT C-KERMIT BINARIES - 3. [20]PLATFORM-SPECIFIC NOTES - 4. [21]GENERAL UNIX-SPECIFIC LIMITATIONS AND BUGS - 5. [22]INITIALIZATION AND COMMAND FILES - 6. [23]COMMUNICATION SPEED SELECTION - 7. [24]COMMUNICATIONS AND DIALING - 8. [25]HARDWARE FLOW CONTROL - 9. [26]TERMINAL CONNECTION AND KEY MAPPING - 10. [27]FILE TRANSFER - 11. [28]EXTERNAL FILE TRANSFER PROTOCOLS - 12. [29]SECURITY - 13. [30]MISCELLANEOUS USER REPORTS - 14. [31]THIRD-PARTY DRIVERS - - Quick Links: [ [32]Linux ] [ [33]*BSD ] [[34]Mac OS X] [ [35]AIX ] [ - [36]HP-UX ] [ [37]Solaris ] [ [38]SCO ] + 1. [20]INTRODUCTION + 2. [21]PREBUILT C-KERMIT BINARIES + 3. [22]PLATFORM-SPECIFIC NOTES + 4. [23]GENERAL UNIX-SPECIFIC LIMITATIONS AND BUGS + 5. [24]INITIALIZATION AND COMMAND FILES + 6. [25]COMMUNICATION SPEED SELECTION + 7. [26]COMMUNICATIONS AND DIALING + 8. [27]HARDWARE FLOW CONTROL + 9. [28]TERMINAL CONNECTION AND KEY MAPPING + 10. [29]FILE TRANSFER + 11. [30]EXTERNAL FILE TRANSFER PROTOCOLS + 12. [31]SECURITY + 13. [32]MISCELLANEOUS USER REPORTS + 14. [33]THIRD-PARTY DRIVERS + + Quick Links: [ [34]Linux ] [ [35]*BSD ] [[36]Mac OS X] [ [37]AIX ] [ + [38]HP-UX ] [ [39]Solaris ] [ [40]SCO ] 1. INTRODUCTION - [ [39]Top ] [ [40]Contents ] [ [41]Next ] + [ [41]Top ] [ [42]Contents ] [ [43]Next ] SECTION CONTENTS - 1.1. [42]Documentation - 1.2. [43]Technical Support - 1.3. [44]The Year 2000 - 1.4. [45]The Euro + 1.1. [44]Documentation + 1.2. [45]Technical Support + 1.3. [46]The Year 2000 + 1.4. [47]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 @@ -75,9 +78,9 @@ CONTENTS 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 [46]Linux, [47]AIX, [48]HP-UX, - [49]Solaris, and so on, and should be read in conjunction with the - [50]platform-independent C-Kermit beware file, which contains similar + specific Unix variations like [48]Linux, [49]AIX, [50]HP-UX, + [51]Solaris, and so on, and should be read in conjunction with the + [52]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). @@ -86,41 +89,41 @@ CONTENTS 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 [51]let me know. + better Web links, please feel free to [53]let me know. 1.1. Documentation - [ [52]Top ] [ [53]Contents ] [ [54]Next ] + [ [54]Top ] [ [55]Contents ] [ [56]Next ] - C-Kermit 6.0 is documented in the book [55]Using C-Kermit, Second + C-Kermit 6.0 is documented in the book [57]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: - [56]Supplement to Using C-Kermit, Second Edition, For C-Kermit 7.0 + [58]Supplement to Using C-Kermit, Second Edition, For C-Kermit 7.0 Thorough documentation of features new to version 7.0. - [57]Supplement to Using C-Kermit, Second Edition, For C-Kermit 8.0 + [59]Supplement to Using C-Kermit, Second Edition, For C-Kermit 8.0 Thorough documentation of features new to version 8.0. - [58]Supplement to Using C-Kermit, Second Edition, For C-Kermit 9.0 + [60]Supplement to Using C-Kermit, Second Edition, For C-Kermit 9.0 Thorough documentation of features new to version 9.0. 1.2. Technical Support - [ [59]Top ] [ [60]Contents ] [ [61]Section Contents ] [ [62]Next ] [ - [63]Previous ] + [ [61]Top ] [ [62]Contents ] [ [63]Section Contents ] [ [64]Next ] [ + [65]Previous ] For information on how to get technical support, please visit: - [64]http://www.columbia.edu/kermit/support.html + [66]http://www.columbia.edu/kermit/support.html 1.3. The Year 2000 - [ [65]Top ] [ [66]Contents ] [ [67]Section Contents ] [ [68]Next ] [ - [69]Previous ] + [ [67]Top ] [ [68]Contents ] [ [69]Section Contents ] [ [70]Next ] [ + [71]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 @@ -167,7 +170,7 @@ CONTENTS 1.4. The Euro - [ [70]Top ] [ [71]Contents ] [ [72]Section Contents ] [ [73]Previous ] + [ [72]Top ] [ [73]Contents ] [ [74]Section Contents ] [ [75]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 @@ -177,7 +180,7 @@ CONTENTS 2. PREBUILT C-KERMIT BINARIES - [ [74]Top ] [ [75]Contents ] [ [76]Next ] [ [77]Previous ] + [ [76]Top ] [ [77]Contents ] [ [78]Next ] [ [79]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 @@ -214,38 +217,38 @@ CONTENTS 3. NOTES ON SPECIFIC UNIX VERSIONS - [ [78]Top ] [ [79]Contents ] [ [80]Next ] [ [81]Previous ] + [ [80]Top ] [ [81]Contents ] [ [82]Next ] [ [83]Previous ] SECTION CONTENTS - 3.0. [82]C-KERMIT ON PC-BASED UNIXES - 3.1. [83]C-KERMIT AND AIX - 3.2. [84]C-KERMIT AND HP-UX - 3.3. [85]C-KERMIT AND LINUX - 3.4. [86]C-KERMIT AND NEXTSTEP - 3.5. [87]C-KERMIT AND QNX - 3.6. [88]C-KERMIT AND SCO - 3.7. [89]C-KERMIT AND SOLARIS - 3.8. [90]C-KERMIT AND SUNOS - 3.9. [91]C-KERMIT AND ULTRIX - 3.10. [92]C-KERMIT AND UNIXWARE - 3.11. [93]C-KERMIT AND APOLLO SR10 - 3.12. [94]C-KERMIT AND TANDY XENIX 3.0 - 3.13. [95]C-KERMIT AND OSF/1 (DIGITAL UNIX) (TRU64 UNIX) - 3.14. [96]C-KERMIT AND SGI IRIX - 3.15. [97]C-KERMIT AND THE BEBOX - 3.16. [98]C-KERMIT AND DG/UX - 3.17. [99]C-KERMIT AND SEQUENT DYNIX - 3.18. [100]C-KERMIT AND {FREE,OPEN,NET}BSD - 3.19. [101]C-KERMIT AND MAC OS X - 3.20. [102]C-KERMIT AND COHERENT + 3.0. [84]C-KERMIT ON PC-BASED UNIXES + 3.1. [85]C-KERMIT AND AIX + 3.2. [86]C-KERMIT AND HP-UX + 3.3. [87]C-KERMIT AND LINUX + 3.4. [88]C-KERMIT AND NEXTSTEP + 3.5. [89]C-KERMIT AND QNX + 3.6. [90]C-KERMIT AND SCO + 3.7. [91]C-KERMIT AND SOLARIS + 3.8. [92]C-KERMIT AND SUNOS + 3.9. [93]C-KERMIT AND ULTRIX + 3.10. [94]C-KERMIT AND UNIXWARE + 3.11. [95]C-KERMIT AND APOLLO SR10 + 3.12. [96]C-KERMIT AND TANDY XENIX 3.0 + 3.13. [97]C-KERMIT AND OSF/1 (DIGITAL UNIX) (TRU64 UNIX) + 3.14. [98]C-KERMIT AND SGI IRIX + 3.15. [99]C-KERMIT AND THE BEBOX + 3.16. [100]C-KERMIT AND DG/UX + 3.17. [101]C-KERMIT AND SEQUENT DYNIX + 3.18. [102]C-KERMIT AND {FREE,OPEN,NET}BSD + 3.19. [103]C-KERMIT AND MAC OS X + 3.20. [104]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: - [103]http://www.faqs.org - [104]http://aplawrence.com/Unixart/newtounix.html + [105]http://www.faqs.org + [106]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 @@ -254,7 +257,7 @@ CONTENTS 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 [105]OS-specific + getty variety, etc). Many examples are given in the [107]OS-specific sections below. An important point to keep in mind is that C-Kermit is a @@ -268,28 +271,28 @@ CONTENTS 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 [106]send us your suggested fixes or changes. Or - else just [107]send us a report about what seems to be wrong and we'll + the source code and [108]send us your suggested fixes or changes. Or + else just [109]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 - [ [108]Top ] [ [109]Contents ] [ [110]Section Contents ] [ [111]Next ] + [ [110]Top ] [ [111]Contents ] [ [112]Section Contents ] [ [113]Next ] - Also see: [112]http://www.pcunix.com/. + Also see: [114]http://www.pcunix.com/. SECTION CONTENTS - 3.0.1. [113]Interrupt Conflicts - 3.0.2. [114]Windows-Specific Hardware - 3.0.3. [115]Modems - 3.0.4. [116]Character Sets - 3.0.5. [117]Keyboard, Screen, and Mouse Access - 3.0.6. [118]Laptops + 3.0.1. [115]Interrupt Conflicts + 3.0.2. [116]Windows-Specific Hardware + 3.0.3. [117]Modems + 3.0.4. [118]Character Sets + 3.0.5. [119]Keyboard, Screen, and Mouse Access + 3.0.6. [120]Laptops 3.0.1. Interrupt Conflicts - [ [119]Top ] [ [120]Contents ] [ [121]Section Contents ] [ [122]Next ] + [ [121]Top ] [ [122]Contents ] [ [123]Section Contents ] [ [124]Next ] PCs are not the best platform for real operating systems like Unix. The architecture suffers from numerous deficiencies, not the least of which @@ -348,8 +351,8 @@ CONTENTS 3.0.2. Windows-Specific Hardware - [ [123]Top ] [ [124]Contents ] [ [125]Section Contents ] [ [126]Next ] - [ [127]Previous ] + [ [125]Top ] [ [126]Contents ] [ [127]Section Contents ] [ [128]Next ] + [ [129]Previous ] To complicate matters, the PC platform is becoming increasingly and inexorably Windows-oriented. More and more add-on devices are "Windows @@ -358,7 +361,7 @@ CONTENTS device itself to do. PCMCIA, PCI, or "Plug-n-Play" devices are rarely supported on PC-based Unix versions such as SCO; Winmodems, Winprinters, and the like are not supported on any Unix variety (with - [128]a few exceptions). The self-proclaimed Microsoft PC 97 (or later) + [130]a few exceptions). The self-proclaimed Microsoft PC 97 (or later) standard only makes matters worse since its only purpose to ensure that PCs are "optimized to run Windows 95 and Windows NT 4.0 and future versions of these operating systems". @@ -370,7 +373,7 @@ CONTENTS matter, all non-Windows operating systems) combined. If your version of Unix (SCO, Linux, BSDI, FreeBSD, etc) does not support a particular device, then C-Kermit can't use it either. C-Kermit, like any Unix - application, must accesss all devices through drivers and not directly + application, must access all devices through drivers and not directly because Unix is a real operating system. Don't waste time thinking that you, or anybody else, could write a @@ -387,7 +390,7 @@ CONTENTS "Legacy Free". One can only speculate what that could mean. Most likely it means it will ONLY run the very latest versions of Windows, and is made exclusively of Winmodems, Winprinters, Winmemory, and Win-CPU-fans - (Legacy Free is a concept [129]pioneered by Microsoft). + (Legacy Free is a concept [131]pioneered by Microsoft). Before you buy a new PC or add-on equipment, especially serial ports, internal modems, or printers, make sure they are compatible with your @@ -406,8 +409,8 @@ CONTENTS 3.0.3. Modems - [ [130]Top ] [ [131]Contents ] [ [132]Section Contents ] [ [133]Next ] - [ [134]Previous ] + [ [132]Top ] [ [133]Contents ] [ [134]Section Contents ] [ [135]Next ] + [ [136]Previous ] External modems are recommended: @@ -430,7 +433,7 @@ CONTENTS software will know how to control it.) For more about Unix compatible modems, see: - [135]http://www.idir.net/~gromitkc/winmodem.html + [137]http://www.idir.net/~gromitkc/winmodem.html Remember that PCs, even now -- more than two decades after they were first introduced -- are not (in general) capable of supporting more @@ -441,14 +444,14 @@ CONTENTS PnP in my computer bios. I was having IRQ conflicts between my serial mouse and 'com 3'. Both modems work fine for me. My first modem is ttyS0 and my second is ttyS1." Special third-party multiport boards - such as [136]DigiBoard are available for certain Unix platforms + such as [138]DigiBoard are available for certain Unix platforms (typically SCO, maybe Linux) that come with special platform-specific drivers. 3.0.4. Character Sets - [ [137]Top ] [ [138]Contents ] [ [139]Section Contents ] [ [140]Next ] - [ [141]Previous ] + [ [139]Top ] [ [140]Contents ] [ [141]Section Contents ] [ [142]Next ] + [ [143]Previous ] PCs generally have PC code pages such as CP437 or CP850, and these are often used by PC-based Unix operating systems, particularly on the @@ -476,8 +479,8 @@ CONTENTS 3.0.5. Keyboard, Screen, and Mouse Access - [ [142]Top ] [ [143]Contents ] [ [144]Section Contents ] [ [145]Next ] - [ [146]Previous ] + [ [144]Top ] [ [145]Contents ] [ [146]Section Contents ] [ [147]Next ] + [ [148]Previous ] Finally, note that as a real operating system, Unix (unlike Windows) does not provide the intimate connection to the PC keyboard, screen, @@ -490,46 +493,46 @@ CONTENTS b. Unix sessions can come from anywhere, not just the PC's own keyboard and screen; and: c. even though it might be possible for an application that actually - is running on the PC's keyboard and screen to accesss these devices + is running on the PC's keyboard and screen to access these devices directly, there are no APIs (outside of X) for this. 3.0.6. Laptops - [ [147]Top ] [ [148]Contents ] [ [149]Section Contents ] [ - [150]Previous ] + [ [149]Top ] [ [150]Contents ] [ [151]Section Contents ] [ + [152]Previous ] (To be filled in . . .) 3.1. C-KERMIT AND AIX - [ [151]Top ] [ [152]Contents ] [ [153]Section Contents ] [ [154]Next ] - [ [155]Previous ] + [ [153]Top ] [ [154]Contents ] [ [155]Section Contents ] [ [156]Next ] + [ [157]Previous ] SECTION CONTENTS - 3.1.1. [156]AIX: General - 3.1.2. [157]AIX: Network Connections - 3.1.3. [158]AIX: Serial Connections - 3.1.4. [159]AIX: File Transfer - 3.1.5. [160]AIX: Xterm Key Map + 3.1.1. [158]AIX: General + 3.1.2. [159]AIX: Network Connections + 3.1.3. [160]AIX: Serial Connections + 3.1.4. [161]AIX: File Transfer + 3.1.5. [162]AIX: Xterm Key Map For additional information see: - * [161]http://www.emerson.emory.edu/services/aix-faq/ - * [162]http://www.faqs.org/faqs/by-newsgroup/comp/comp.unix.aix.html - * [163]http://www.cis.ohio-state.edu/hypertext/faq/usenet/aix-faq/top + * [163]http://www.emerson.emory.edu/services/aix-faq/ + * [164]http://www.faqs.org/faqs/by-newsgroup/comp/comp.unix.aix.html + * [165]http://www.cis.ohio-state.edu/hypertext/faq/usenet/aix-faq/top .html - * [164]http://aixpdslib.seas.ucla.edu/ - * [165]http://www.rootvg.net (AIX history) - * [166]ftp://rtfm.mit.edu/pub/usenet/news.answers/aix-faq/part1 - * [167]ftp://mirrors.aol.com/pub/rtfm/usenet-by-hierarchy/comp/unix/a + * [166]http://aixpdslib.seas.ucla.edu/ + * [167]http://www.rootvg.net (AIX history) + * [168]ftp://rtfm.mit.edu/pub/usenet/news.answers/aix-faq/part1 + * [169]ftp://mirrors.aol.com/pub/rtfm/usenet-by-hierarchy/comp/unix/a ix - and/or read the [168]comp.unix.aix newsgroup. + and/or read the [170]comp.unix.aix newsgroup. ________________________________________________________________________ 3.1.1. AIX: General - [ [169]Top ] [ [170]Contents ] [ [171]Section Contents ] [ [172]Next ] + [ [171]Top ] [ [172]Contents ] [ [173]Section Contents ] [ [174]Next ] About AIX version numbers: "uname -a" tells the two-digit version number, such as 3.2 or 4.1. The three-digit form can be seen with the @@ -548,8 +551,8 @@ CONTENTS 3.1.2. AIX: Network Connections - [ [173]Top ] [ [174]Contents ] [ [175]Section Contents ] [ [176]Next ] - [ [177]Previous ] + [ [175]Top ] [ [176]Contents ] [ [177]Section Contents ] [ [178]Next ] + [ [179]Previous ] File transfers into AIX 4.2 or 4.3 through the AIX Telnet or Rlogin server have been observed to fail (or accumulate huge numbers of @@ -563,7 +566,7 @@ CONTENTS removed from the picture; e.g, by using "set host * 3000" on AIX. The problem can be completely cured by replacing the IBM Telnet server - with [178]MIT's Kerberos Telnet server -- even if you don't actually + with [180]MIT's Kerberos Telnet server -- even if you don't actually use the Kerberos part. Diagnosis: AIX pseudoterminals (which are controlled by the Telnet server to give you a login terminal for your session) have quirks that not even IBM knows about. The situation with @@ -625,15 +628,15 @@ CONTENTS 3.1.3. AIX: Serial Connections - [ [179]Top ] [ [180]Contents ] [ [181]Section Contents ] [ [182]Next ] - [ [183]Previous ] + [ [181]Top ] [ [182]Contents ] [ [183]Section Contents ] [ [184]Next ] + [ [185]Previous ] In AIX 3, 4, or 5, C-Kermit won't be able to "set line /dev/tty0" (or any other dialout device) if you haven't installed "cu" or "uucp" on your system, because installing these is what creates the UUCP lockfile - directory. If SET LINE commands always result in "Sorry, accesss to - lock denied", even when C-Kermit has been given the same owner, group, - and permissions as cu: + directory. If SET LINE commands always result in "Sorry, access to lock + denied", even when C-Kermit has been given the same owner, group, and + permissions as cu: -r-sr-xr-x 1 uucp uucp 67216 Jul 27 1999 cu @@ -719,7 +722,7 @@ CONTENTS /dev/tty, as opposed to a specify port device). 3. Fixes for bugs in the original AIX 4.2 tty (serial i/o) support and other AIX bugs are available from IBM at: - [184]http://service.software.ibm.com/rs6000/ + [186]http://service.software.ibm.com/rs6000/ Downloads -> Software Fixes -> Download FixDist gets an application for looking up known problems. @@ -735,8 +738,8 @@ CONTENTS 3.1.4. AIX: File Transfer - [ [185]Top ] [ [186]Contents ] [ [187]Section Contents ] [ [188]Next ] - [ [189]Previous ] + [ [187]Top ] [ [188]Contents ] [ [189]Section Contents ] [ [190]Next ] + [ [191]Previous ] Evidently AIX 4.3 (I don't know about earlier versions) does not allow open files to be overwritten. This can cause Kermit transfers to fail @@ -811,8 +814,8 @@ CONTENTS 3.1.5. AIX: Xterm Key Map - [ [190]Top ] [ [191]Contents ] [ [192]Section Contents ] [ - [193]Previous ] + [ [192]Top ] [ [193]Contents ] [ [194]Section Contents ] [ + [195]Previous ] Here is a sample configuration for setting up an xterm keyboard for VT220 or higher terminal emulation on AIX, courtesy of Bruce Momjian, @@ -879,21 +882,21 @@ CONTENTS 3.2. C-KERMIT AND HP-UX - [ [194]Top ] [ [195]Contents ] [ [196]Section Contents ] [ [197]Next ] - [ [198]Previous ] + [ [196]Top ] [ [197]Contents ] [ [198]Section Contents ] [ [199]Next ] + [ [200]Previous ] SECTION CONTENTS - 3.2.0. [199]Common Problems - 3.2.1. [200]Building C-Kermit on HP-UX - 3.2.2. [201]File Transfer - 3.2.3. [202]Dialing Out and UUCP Lockfiles in HP-UX - 3.2.4. [203]Notes on Specific HP-UX Releases - 3.2.5. [204]HP-UX and X.25 + 3.2.0. [201]Common Problems + 3.2.1. [202]Building C-Kermit on HP-UX + 3.2.2. [203]File Transfer + 3.2.3. [204]Dialing Out and UUCP Lockfiles in HP-UX + 3.2.4. [205]Notes on Specific HP-UX Releases + 3.2.5. [206]HP-UX and X.25 REFERENCES - For further information, read the [205]comp.sys.hp.hpux newsgroup. + For further information, read the [207]comp.sys.hp.hpux newsgroup. C-Kermit is included as part of the HP-UX operating system by contract between Hewlett Packard and Columbia University for HP-UX 10.00 and @@ -914,7 +917,7 @@ CONTENTS 3.2.0. Common Problems - [ [206]Top ] [ [207]Contents ] [ [208]Section Contents ] [ [209]Next ] + [ [208]Top ] [ [209]Contents ] [ [210]Section Contents ] [ [211]Next ] Some HP workstations have a BREAK/RESET key. If you hit this key while C-Kermit is running, it might kill or suspend the C-Kermit process. @@ -945,8 +948,8 @@ CONTENTS 3.2.1. Building C-Kermit on HP-UX - [ [210]Top ] [ [211]Contents ] [ [212]Section Contents ] [ [213]Next ] - [ [214]Previous ] + [ [212]Top ] [ [213]Contents ] [ [214]Section Contents ] [ [215]Next ] + [ [216]Previous ] This section applies mainly to old (pre-10.20) HP-UX version on old, slow, and/or memory-constrained hardware. @@ -975,7 +978,7 @@ CONTENTS The optimizing compiler might complain about "some optimizations skipped" on certain modules, due to lack of space available to the optimizer. You can increase the space (the incantation depends on the - particular compiler version -- see the [215]makefile), but doing so + particular compiler version -- see the [217]makefile), but doing so tends to make the compilations take a much longer time. For example, the "hpux0100o+" makefile target adds the "+Onolimit" compiler flag, and about an hour to the compile time on an HP-9000/730. But it *does* @@ -986,8 +989,8 @@ CONTENTS 3.2.2. File Transfer - [ [216]Top ] [ [217]Contents ] [ [218]Section Contents ] [ [219]Next ] - [ [220]Previous ] + [ [218]Top ] [ [219]Contents ] [ [220]Section Contents ] [ [221]Next ] + [ [222]Previous ] Telnet connections into HP-UX versions up to and including 11.11 (and possibly 11.20) tend not to lend themselves to file transfer due to @@ -1105,8 +1108,8 @@ CONTENTS 3.2.3. Dialing Out and UUCP Lockfiles in HP-UX - [ [221]Top ] [ [222]Contents ] [ [223]Section Contents ] [ [224]Next ] - [ [225]Previous ] + [ [223]Top ] [ [224]Contents ] [ [225]Section Contents ] [ [226]Next ] + [ [227]Previous ] HP workstations do not come with dialout devices configured; you have to do it yourself (as root). First look in /dev to see what's there; @@ -1177,9 +1180,9 @@ CONTENTS through a true null modem). Do not use the ttydp device for dialing out. - Kermit's accesss to serial devices is controlled by "UUCP lockfiles", + Kermit's access to serial devices is controlled by "UUCP lockfiles", which are intended to prevent different users using different software - programs (Kermit, cu, etc, and UUCP itself) from accesssing the same + programs (Kermit, cu, etc, and UUCP itself) from accessing the same serial device at the same time. When a device is in use by a particular user, a file with a special name is created in: @@ -1193,7 +1196,7 @@ CONTENTS installed setuid to the owner (bin) of the serial device and setgid to the group (daemon) of the /var/spool/locks directory. Kermit's setuid and setgid privileges are enabled only when opening the device and - accesssing the lockfiles. + accessing the lockfiles. Let's say "unit" means a string of decimal digits (the interface instance number) followed (in HP-UX 10.00 and later) by the letter "p" @@ -1224,7 +1227,7 @@ CONTENTS In other words, if the device name begins with "cu", a second lockfile for the "ttyd" device, same unit, is created, which should prevent - dialin accesss on that device. + dialin access on that device. The case allows for symbolic links, etc, but of course it is not foolproof since we have no way of telling which device is really @@ -1255,7 +1258,7 @@ CONTENTS When the "set line" command succeeds in HP-UX 10.00 and later, C-Kermit also creates a Unix System V R4 "advisory lock" as a further precaution - (but not guarantee) against any other process obtaining accesss to the + (but not guarantee) against any other process obtaining access to the device while you are using it. If the selected device was in use by "cu", Kermit can't open it, @@ -1310,17 +1313,17 @@ CONTENTS SECTION CONTENTS - 3.2.4.1. [226]HP-UX 11 - 3.2.4.2. [227]HP-UX 10 - 3.2.4.3. [228]HP-UX 9 - 3.2.4.4. [229]HP-UX 8 - 3.2.4.5. [230]HP-UX 7 and Earlier + 3.2.4.1. [228]HP-UX 11 + 3.2.4.2. [229]HP-UX 10 + 3.2.4.3. [230]HP-UX 9 + 3.2.4.4. [231]HP-UX 8 + 3.2.4.5. [232]HP-UX 7 and Earlier 3.2.4.1. HP-UX 11 - [ [231]Top ] [ [232]Contents ] [ [233]Section Contents ] [ [234]Next ] + [ [233]Top ] [ [234]Contents ] [ [235]Section Contents ] [ [236]Next ] - As noted in [235]Section 3.2.2, the HP-UX 11 Telnet server and/or + As noted in [237]Section 3.2.2, the HP-UX 11 Telnet server and/or pseudoterminal driver are a serious impediment to file transfer over Telnet connections into HP-UX. If you have a Telnet connection into HP-UX 11, tell your desktop Kermit program to: @@ -1354,8 +1357,8 @@ CONTENTS 3.2.4.2. HP-UX 10 - [ [236]Top ] [ [237]Contents ] [ [238]Section Contents ] [ [239]Next ] - [ [240]Previous ] + [ [238]Top ] [ [239]Contents ] [ [240]Section Contents ] [ [241]Next ] + [ [242]Previous ] Beginning in HP-UX 10.10, libcurses is linked to libxcurses, the new UNIX95 (X/Open) version of curses, which has some serious bugs; some @@ -1380,8 +1383,8 @@ CONTENTS 3.2.4.3. HP-UX 9 - [ [241]Top ] [ [242]Contents ] [ [243]Section Contents ] [ [244]Next ] - [ [245]Previous ] + [ [243]Top ] [ [244]Contents ] [ [245]Section Contents ] [ [246]Next ] + [ [247]Previous ] HP-UX 9.00 and 9.01 need patch PHNE_10572 (note: this replaces PHNE_3641) for hptt0.o, asio0.o, and ttycomn.o in libhp-ux.a. Contact @@ -1406,8 +1409,8 @@ CONTENTS 3.2.4.4. HP-UX 8 - [ [246]Top ] [ [247]Contents ] [ [248]Section Contents ] [ [249]Next ] - [ [250]Previous ] + [ [248]Top ] [ [249]Contents ] [ [250]Section Contents ] [ [251]Next ] + [ [252]Previous ] To make C-Kermit work on HP-UX 8.05 on a model 720, obtain and install HP-UX patch PHNE_0899. This patch deals with a lot of driver issues, @@ -1428,8 +1431,8 @@ CONTENTS 3.2.4.5. HP-UX 7 and Earlier - [ [251]Top ] [ [252]Contents ] [ [253]Section Contents ] [ - [254]Previous ] + [ [253]Top ] [ [254]Contents ] [ [255]Section Contents ] [ + [256]Previous ] When transferring files into HP-UX 5 or 6 over a Telnet connection, you must not use streaming, and you must not use a packet length greater @@ -1460,8 +1463,8 @@ CONTENTS 3.2.5. HP-UX and X.25 - [ [255]Top ] [ [256]Contents ] [ [257]Section Contents ] [ - [258]Previous ] + [ [257]Top ] [ [258]Contents ] [ [259]Section Contents ] [ + [260]Previous ] Although C-Kermit presently does not include built-in support for HP-UX X.25 (as it does for the Sun and IBM X.25 products), it can still be @@ -1477,17 +1480,17 @@ CONTENTS 3.3. C-KERMIT AND LINUX - [ [259]Top ] [ [260]Contents ] [ [261]Section Contents ] [ [262]Next ] - [ [263]Previous ] + [ [261]Top ] [ [262]Contents ] [ [263]Section Contents ] [ [264]Next ] + [ [265]Previous ] SECTION CONTENTS - 3.3.1. [264]Problems Building C-Kermit for Linux - 3.3.2. [265]Problems with Serial Devices in Linux - 3.3.3. [266]Terminal Emulation in Linux - 3.3.4. [267]Dates and Times - 3.3.5. [268]Startup Errors - 3.3.6. [269]The Fullscreen File Transfer Display + 3.3.1. [266]Problems Building C-Kermit for Linux + 3.3.2. [267]Problems with Serial Devices in Linux + 3.3.3. [268]Terminal Emulation in Linux + 3.3.4. [269]Dates and Times + 3.3.5. [270]Startup Errors + 3.3.6. [271]The Fullscreen File Transfer Display (August 2010) Reportedly C-Kermit packages for certain Linux distributions such as Centos and Ubuntu have certain features @@ -1505,7 +1508,7 @@ write(3, "RESOLVE-ADDRESS 255.255.255.255\n", 32) This is not Kermit Project code. Turns out to be something in glibc's resolver, and can be fixed by changing /etc/nsswitch.conf, - but it might break other software, such as [270]Avahi or anything + but it might break other software, such as [272]Avahi or anything (such as Gnome, Java, or Cups) that depends on it. I'm not sure where it happens; I don't think Kermit tries to get its IP address at startup time, only when it's needed or asked for, e.g. when @@ -1513,50 +1516,50 @@ write(3, "RESOLVE-ADDRESS 255.255.255.255\n", 32) REFERENCES - For further information, read the [271]comp.os.linux.misc, - [272]comp.os.linux.answers, and other Linux-oriented newsgroups, and + For further information, read the [273]comp.os.linux.misc, + [274]comp.os.linux.answers, and other Linux-oriented newsgroups, and see: The Linux Document Project (LDP) - [273]http://www.tldp.org/ + [275]http://www.tldp.org/ The Linux FAQ - [274]http://www.tldp.org/FAQ/Linux-FAQ.html + [276]http://www.tldp.org/FAQ/Linux-FAQ.html The Linux HOWTOs (especially the Serial HOWTO) - [275]http://www.tldp.org/HOWTO/Serial-HOWTO.html + [277]http://www.tldp.org/HOWTO/Serial-HOWTO.html - [276]http://tldp.org/HOWTO/Modem-HOWTO.html + [278]http://tldp.org/HOWTO/Modem-HOWTO.html - [277]ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO + [279]ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO - [278]ftp://tsx-11.mit.edu/pub/linux/docs/HOWTO + [280]ftp://tsx-11.mit.edu/pub/linux/docs/HOWTO - [279]http://www.tldp.org/HOWTO/ + [281]http://www.tldp.org/HOWTO/ - [280]http://www.tldp.org/hmirrors.html + [282]http://www.tldp.org/hmirrors.html Linux Vendor Tech Support Pages: - [281]http://www.redhat.com/apps/support/ + [283]http://www.redhat.com/apps/support/ - [282]http://www.debian.org/support + [284]http://www.debian.org/support - [283]http://www.slackware.com/support/ + [285]http://www.slackware.com/support/ - [284]http://www.caldera.com/support/ + [286]http://www.caldera.com/support/ - [285]SUSE Linux Support + [287]SUSE Linux Support - [286]http://www.mandrake.com/support/ + [288]http://www.mandrake.com/support/ - [287]http://www.turbolinux.com/support/ + [289]http://www.turbolinux.com/support/ Linux Winmodem Support - [288]http://www.linmodems.org/ + [290]http://www.linmodems.org/ - Also see general comments on PC-based Unixes in [289]Section 3.0. + Also see general comments on PC-based Unixes in [291]Section 3.0. What Linux version is it? -- "uname -a" supplies only kernel information, but these days it's the distribution that matters: Red Hat @@ -1570,17 +1573,17 @@ write(3, "RESOLVE-ADDRESS 255.255.255.255\n", 32) Did you know: DECnet is available for Linux? See: - [290]http://linux.dreamtime.org/decnet/ + [292]http://linux.dreamtime.org/decnet/ (But there is no support for it in C-Kermit -- anybody interested in - adding it, please [291]let me know). + adding it, please [293]let me know). Before proceeding, let's handle the some of the most frequently asked question in the Linux newsgroups: 1. Neither C-Kermit nor any other Linux application can use Winmodems, - except in the [292]rare cases where Linux drivers have been written - for them. See [293]Section 3.0.2 for details. + except in the [294]rare cases where Linux drivers have been written + for them. See [295]Section 3.0.2 for details. 2. "Why does it take such a long time to make a telnet connection to (or from) my Linux PC?" (this applies to C-Kermit and to regular Telnet). Most telnet servers these days perform reverse DNS lookups @@ -1602,9 +1605,9 @@ write(3, "RESOLVE-ADDRESS 255.255.255.255\n", 32) thought to be secure, whereas Telnet is thought to be insecure. This is true for clear-text Telnet (because passwords travel in the clear across the network), but apparently few people realize that - [294]secure Telnet clients and servers have been available for + [296]secure Telnet clients and servers have been available for years, and these are more secure than SSH (for reasons explained - [295]HERE). + [297]HERE). 4. (Any question that has the word "FTP" in it...) The knee-jerk reaction being "Don't use FTP, use SCP!" (or SFTP). Same answer as above, but moreso. SCP and SFTP are not only not platform neutral, @@ -1618,7 +1621,7 @@ write(3, "RESOLVE-ADDRESS 255.255.255.255\n", 32) 3.3.1. Problems Building C-Kermit for Linux - [ [296]Top ] [ [297]Contents ] [ [298]Section Contents ] [ [299]Next ] + [ [298]Top ] [ [299]Contents ] [ [300]Section Contents ] [ [301]Next ] Modern Linux distributions like Red Hat give you a choice at installation whether to include "developer tools". Obviously, you can't @@ -1645,17 +1648,17 @@ write(3, "RESOLVE-ADDRESS 255.255.255.255\n", 32) 3.3.2. Problems with Serial Devices in Linux - [ [300]Top ] [ [301]Contents ] [ [302]Section Contents ] [ [303]Next ] - [ [304]Previous ] + [ [302]Top ] [ [303]Contents ] [ [304]Section Contents ] [ [305]Next ] + [ [306]Previous ] Also see: "man setserial", "man irqtune". - And: [305]Sections 3.0, [306]6, [307]7, and [308]8 of this document. + And: [307]Sections 3.0, [308]6, [309]7, and [310]8 of this document. NOTE: Red Hat Linux 7.2 and later include a new API that allows serial-port arbitration by non-setuid/gid programs. This API has not yet been added to C-Kermit. If C-Kermit is to be used for dialing out on Red Hat 7.2 or later, it must still be installed as described - in in Sections [309]10 and [310]11 of the [311]Installation + in in Sections [311]10 and [312]11 of the [313]Installation Instructions. Don't expect it to be easy. Queries like the following are posted to @@ -1684,7 +1687,7 @@ write(3, "RESOLVE-ADDRESS 255.255.255.255\n", 32) setserial -g /dev/cua1 tells me that the uart is 'unknown'. I have tried setting the UART - manullay via. setserial to 16550A, 16550, and the other one (8550?) + manually via. setserial to 16550A, 16550, and the other one (8550?) (I didn't try 16540). None of these manual settings resulted in any success. @@ -1735,7 +1738,7 @@ $ cat /proc/interrupts 15: 6 XT-PIC ide1 Watch out for PCI, PCMCIA and Plug-n-Play devices, Winmodems, and the - like (see cautions in [312]Section 3.0 Linux supports Plug-n-Play + like (see cautions in [314]Section 3.0 Linux supports Plug-n-Play devices to some degree via the isapnp and pnpdump programs; read the man pages for them. (If you don't have them, look on your installation CD for isapnptool or download it from sunsite or a sunsite mirror or @@ -1810,7 +1813,7 @@ $ cat /proc/interrupts will phase (have phased) it out in favor of the ttyS device. See (if it's still there): - [313]http://linuxwww.db.erau.edu/mail_archives/linux-kernel/Mar_98/1441.html + [315]http://linuxwww.db.erau.edu/mail_archives/linux-kernel/Mar_98/1441.html (no, of course it isn't; you'll have to use your imagination). One user reported that C-Kermit 7.0, when built with egcs 1.1.2 and run on Linux @@ -1831,11 +1834,11 @@ $ cat /proc/interrupts 3.3.3. Terminal Emulation in Linux - [ [314]Top ] [ [315]Contents ] [ [316]Section Contents ] [ [317]Next ] - [ [318]Previous ] + [ [316]Top ] [ [317]Contents ] [ [318]Section Contents ] [ [319]Next ] + [ [320]Previous ] C-Kermit is not a terminal emulator. For a brief explanation of why - not, see [319]Section 3.0.5. For a fuller explanation, [320]ClICK HERE. + not, see [321]Section 3.0.5. For a fuller explanation, [322]ClICK HERE. In Unix, terminal emulation is supplied by the Window in which you run Kermit: the regular console screen, which provides Linux Console @@ -1843,7 +1846,7 @@ $ cat /proc/interrupts xterm window, which gives VTxxx emulation. An xterm that includes color ANSI and VT220 emulation is available with Xfree86: - [321]http://dickey.his.com/xterm/xterm.html + [323]http://dickey.his.com/xterm/xterm.html Before starting C-Kermit in an xterm window, you might need to tell the xterm window's shell to "stty sane". @@ -1878,13 +1881,13 @@ $ cat /proc/interrupts Console-mode keys are mapped separately using loadkeys, and different keycodes are used. Find out what they are with showkey. - For a much more complete VT220/320 key mapping for [322]Xfree86 xterm, - [323]CLICK HERE. + For a much more complete VT220/320 key mapping for [324]Xfree86 xterm, + [325]CLICK HERE. 3.3.4. Dates and Times - [ [324]Top ] [ [325]Contents ] [ [326]Section Contents ] [ [327]Next ] - [ [328]Previous ] + [ [326]Top ] [ [327]Contents ] [ [328]Section Contents ] [ [329]Next ] + [ [330]Previous ] If C-Kermit's date-time (e.g. as shown by its DATE command) differs from the system's date and time: @@ -1897,8 +1900,8 @@ $ cat /proc/interrupts 3.3.5. Startup Errors - [ [329]Top ] [ [330]Contents ] [ [331]Section Contents ] [ [332]Next ] - [ [333]Previous ] + [ [331]Top ] [ [332]Contents ] [ [333]Section Contents ] [ [334]Next ] + [ [335]Previous ] C-Kermit should work on all versions of Linux current through March 2003, provided it was built on the same version you have, with the same @@ -1908,8 +1911,8 @@ $ cat /proc/interrupts C-Kermit binary will not stop working at a later date, since Linux tends to change out from under its applications. If that happens, rebuild C-Kermit from source. If something goes wrong with the build - process, look on the [334]C-Kermit website for a newer version. If you - have the latest version, then [335]report the problem to us. + process, look on the [336]C-Kermit website for a newer version. If you + have the latest version, then [337]report the problem to us. Inability to transfer files in Red Hat 7.2: the typical symptom would be if you start Kermit and tell it to RECEIVE, it fails right away with @@ -1927,7 +1930,7 @@ $ cat /proc/interrupts assigning a controlling TTY for the session, which would make most use of "/dev/tty" somewhat less than useful. - [336]http://www.redhat.com/support/errata/RHBA-2001-153.html + [338]http://www.redhat.com/support/errata/RHBA-2001-153.html Quoting: "Due to terminal handling problems in /bin/login, tcsh would not find the controlling terminal correctly, and a shell in single user @@ -1939,7 +1942,7 @@ $ cat /proc/interrupts Kermit RPM for Red Hat Linux, not working; either it won't start at all, or it gives error messages about "terminal type unknown" and refuses to initialize its curses support. The following is from the - [337]Kermit newsgroup: + [339]Kermit newsgroup: From: rchandra@hal9000.buf.servtech.com Newsgroups: comp.protocols.kermit.misc @@ -1977,7 +1980,7 @@ $ cat /proc/interrupts ln -s /usr/share/terminfo /usr/lib/terminfo So what this says is that the terminfo database/directory structure - can be accesssed by either path. When something goes to reference + can be accessed by either path. When something goes to reference /usr/lib/terminfo, the symlink redirects it to essentially /usr/share/terminfo, which is where it really resides on your system. I personally prefer wherever possible to use relative @@ -1991,8 +1994,8 @@ $ cat /proc/interrupts 3.3.6. The Fullscreen File Transfer Display - [ [338]Top ] [ [339]Contents ] [ [340]Section Contents ] [ - [341]Previous ] + [ [340]Top ] [ [341]Contents ] [ [342]Section Contents ] [ + [343]Previous ] Starting with ncurses versions dated 1998-12-12 (about a year before ncurses 5.0), ncurses sets the terminal for buffered i/o, but @@ -2019,8 +2022,8 @@ $ cat /proc/interrupts 3.4. C-KERMIT AND NEXTSTEP - [ [342]Top ] [ [343]Contents ] [ [344]Section Contents ] [ [345]Next ] - [ [346]Previous ] + [ [344]Top ] [ [345]Contents ] [ [346]Section Contents ] [ [347]Next ] + [ [348]Previous ] Run C-Kermit in a Terminal, Stuart, or xterm window, or when logged in remotely through a serial port or TELNET connection. C-Kermit does not @@ -2077,10 +2080,10 @@ $ cat /proc/interrupts 3.5. C-KERMIT AND QNX - [ [347]Top ] [ [348]Contents ] [ [349]Section Contents ] [ [350]Next ] - [ [351]Previous ] + [ [349]Top ] [ [350]Contents ] [ [351]Section Contents ] [ [352]Next ] + [ [353]Previous ] - See also: The [352]comp.os.qnx newsgroup. + See also: The [354]comp.os.qnx newsgroup. Support for QNX 4.x was added in C-Kermit 5A(190). This is a full-function implementation, thoroughly tested on QNX 4.21 and later, @@ -2089,7 +2092,7 @@ $ cat /proc/interrupts successfully (after stripping most most features, I succeeded in getting it to compile and link without complaint, but the executable just beeps when you run it); for 16-bit QNX 4.2x, use C-Kermit 6.0 or - earlier, or else [353]G-Kermit. + earlier, or else [355]G-Kermit. The 32-bit version (and the 16-bit version prior to C-Kermit 7.0) supports most of C-Kermit's advanced features including TCP/IP, high @@ -2118,8 +2121,8 @@ $ cat /proc/interrupts UUCP line locking. If you have a UUCP product installed on your QNX system, remove the -DNOUUCP switch from the makefile entry and rebuild. Then check to see that Kermit's UUCP lockfile conventions are the same - as those of your UUCP package; if not, read the [354]UUCP lockfile - section of the [355]Installation Instructions and make the necessary + as those of your UUCP package; if not, read the [356]UUCP lockfile + section of the [357]Installation Instructions and make the necessary changes to the makefile entry (e.g. add -DHDBUUCP). QNX does, however, allow a program to get the device open count. This @@ -2145,62 +2148,62 @@ $ cat /proc/interrupts 3.6. C-KERMIT AND SCO - [ [356]Top ] [ [357]Contents ] [ [358]Section Contents ] [ [359]Next ] - [ [360]Previous ] + [ [358]Top ] [ [359]Contents ] [ [360]Section Contents ] [ [361]Next ] + [ [362]Previous ] SECTION CONTENTS -3.6.1. [361]SCO XENIX -3.6.2. [362]SCO UNIX and OSR5 -3.6.3. [363]Unixware -3.6.4. [364]Open UNIX 8 +3.6.1. [363]SCO XENIX +3.6.2. [364]SCO UNIX and OSR5 +3.6.3. [365]Unixware +3.6.4. [366]Open UNIX 8 REFERENCES * The comp.unix.sco.* newsgroups. - * [365]Section 3.10 below for Unixware. + * [367]Section 3.10 below for Unixware. * The following FAQs: The comp.sco.misc FAQ: - [366]http://aplawrence.com/SCOFAQ/ + [368]http://aplawrence.com/SCOFAQ/ Caldera (SCO) comp.unix.sco.programmer FAQ: - [367]http://www.zenez.com/cgi-bin/scoprogfaq/faq.pl + [369]http://www.zenez.com/cgi-bin/scoprogfaq/faq.pl The UnixWare 7/OpenUNIX 8 FAQ: - [368]http://www.zenez.com/cgi-bin/scouw7faq/faq.pl - [369]http://zenez.pcunix.com/cgi-bin/scouw7faq/faq.pl + [370]http://www.zenez.com/cgi-bin/scouw7faq/faq.pl + [371]http://zenez.pcunix.com/cgi-bin/scouw7faq/faq.pl High Speed Modems for SCO Unix: - [370]http://pcunix.com/Unixart/modems.html + [372]http://pcunix.com/Unixart/modems.html The UnixWare FAQ - [371]http://www.freebird.org/faq/ + [373]http://www.freebird.org/faq/ The UnixWare 1.x and 2.0 Programmer FAQ - [372]http://www.freebird.org/faq/developer.html + [374]http://www.freebird.org/faq/developer.html Caldera Support Knowledge Base - [373]http://support.caldera.com/caldera + [375]http://support.caldera.com/caldera - [374]http://stage.caldera.com/ta/ + [376]http://stage.caldera.com/ta/ Caldera (SCO) Technical Article Search Center - [375]http://aplawrence.com/newtosco.html + [377]http://aplawrence.com/newtosco.html New to SCO (Tony Lawrence) The same comments regarding terminal emulation and key mapping apply to SCO operating systems as to all other Unixes. C-Kermit is not a terminal emulator, and you can't use it to map F-keys, Arrow keys, etc. The way to do this is with xmodmap (xterm) or loadkeys (console). For a - brief explanation, see [376]Section 3.0.5. For a fuller explanation, - [377]ClICK HERE. + brief explanation, see [378]Section 3.0.5. For a fuller explanation, + [379]ClICK HERE. - Also see general comments on PC-based Unixes in [378]Section 3.0. + Also see general comments on PC-based Unixes in [380]Section 3.0. 3.6.1. SCO XENIX - [ [379]Top ] [ [380]Contents ] [ [381]Section Contents ] [ [382]Next ] + [ [381]Top ] [ [382]Contents ] [ [383]Section Contents ] [ [384]Next ] Old Xenix versions... Did you know: Xenix 3.0 is *older* than Xenix 2.0? @@ -2209,7 +2212,7 @@ $ cat /proc/interrupts DTR to hang up a modem does not work. DTR goes down but does not come up again. Workaround: Use SET MODEM HANGUP-METHOD MODEM-COMMAND. Anybody who would like to fix this is welcome to take a look at - tthang() in [383]ckutio.c. Also: modem signals can not be read in + tthang() in [385]ckutio.c. Also: modem signals can not be read in Xenix, and the maximum serial speed is 38400. There is all sorts of confusion among SCO versions, particularly when @@ -2222,15 +2225,15 @@ $ cat /proc/interrupts Xenix 2.3.0 and later claim to support RTSFLOW and CTSFLOW, but this is not modern bidirectional hardware flow control; rather it implements the original RS-232 meanings of these signals for unidirectional - half-duplex line accesss: If both RTSFLOW and CTSFLOW bits are set, + half-duplex line access: If both RTSFLOW and CTSFLOW bits are set, Xenix asserts RTS when it wants to send data and waits for CTS assertion before it actually starts sending data (also, reportedly, even this is broken in Xenix 2.3.0 and 2.3.1). 3.6.2. SCO UNIX AND OSR5 - [ [384]Top ] [ [385]Contents ] [ [386]Section Contents ] [ [387]Next ] - [ [388]Previous ] + [ [386]Top ] [ [387]Contents ] [ [388]Section Contents ] [ [389]Next ] + [ [390]Previous ] SCO systems tend to use different names (i.e. drivers) for the same device. Typically /dev/tty1a refers to a terminal device that has no @@ -2262,7 +2265,7 @@ $ cat /proc/interrupts using third-party drivers. (Example: hardware flow control works, reportedly, only on uppercase device like tty1A -- not tty1a -- and only when CLOCAL is clear when using the SCO sio driver, but there are - no such restrictions in, e.g., [389]Digiboard drivers). + no such restrictions in, e.g., [391]Digiboard drivers). One user reports that he can't transfer large files with C-Kermit under SCO OSR5.0.0 and 5.0.4 -- after the first 5K, everything falls apart. @@ -2270,7 +2273,7 @@ $ cat /proc/interrupts Later, he said that replacing SCO's SIO driver with FAS, an alternative communications driver, made the problem go away: - [390]ftp://ftp.fu-berlin.de/pub/unix/driver/fas + [392]ftp://ftp.fu-berlin.de/pub/unix/driver/fas With regard to bidirectional serial ports on OpenServer 5.0.4, the following advice appeared on an SCO-related newsgroup: @@ -2305,14 +2308,14 @@ $ cat /proc/interrupts One SCO user of C-Kermit 5A(190) reported that only one copy of Kermit can run at a time when a Stallion Technologies multiport boards are - installed. Cause, cure, and present status unknown (see [391]Section 14 + installed. Cause, cure, and present status unknown (see [393]Section 14 for more info regarding Stallion). Prior to SCO OpenServer 5.0.4, the highest serial port speed supported by SCO was 38400. However, in some SCO versions (e.g. OSR5) it is possible to map rarely-used lower speeds (like 600 and 1800) to higher ones like 57600 and 115200. To find out how, go to - [392]http://www.sco.com/ and search for "115200". In OSR5.0.4, serial + [394]http://www.sco.com/ and search for "115200". In OSR5.0.4, serial speeds up to 921600 are supported through the POSIX interface; C-Kermit 6.1.193 or later, when built for OSR5.0.4 using /bin/cc (NOT the UDK, which hides the high-speed definitions from CPP), supports these @@ -2335,7 +2338,7 @@ $ cat /proc/interrupts SCO OpenServer Release 5.0.4 or later SCO Internet FastStart Release 1.0.0 or later - SCO supplements are at [393]ftp://ftp.sco.com/; the "rs40" series are + SCO supplements are at [395]ftp://ftp.sco.com/; the "rs40" series are under directory /Supplements/internet Kermit includes the high serial speeds in all OSR5 builds, but that @@ -2388,11 +2391,11 @@ $ cat /proc/interrupts 3.6.3. Unixware - [ [394]Top ] [ [395]Contents ] [ [396]Section Contents ] [ [397]Next ] - [ [398]Previous ] + [ [396]Top ] [ [397]Contents ] [ [398]Section Contents ] [ [399]Next ] + [ [400]Previous ] Unixware changed hands several times before landing at SCO, and so has - its [399]own section in this document. (Briefly: AT&T UNIX Systems + its [401]own section in this document. (Briefly: AT&T UNIX Systems Laboratories sold the rights to the UNIX name and to System V R4 (or R5?) to Novell; later Novell spun its UNIX division off into a new company called Univel, which eventually was bought by SCO, which later @@ -2400,8 +2403,8 @@ $ cat /proc/interrupts 3.6.4. Open UNIX 8 - [ [400]Top ] [ [401]Contents ] [ [402]Section Contents ] [ - [403]Previous ] + [ [402]Top ] [ [403]Contents ] [ [404]Section Contents ] [ + [405]Previous ] SCO was bought by Caldera in 2000 or 2001 and evolved Unixware 7.1 into Caldera Open UNIX 8.00. It's just like Unixware 7.1 as far as Kermit is @@ -2413,47 +2416,47 @@ $ cat /proc/interrupts 3.7. C-KERMIT AND SOLARIS - [ [404]Top ] [ [405]Contents ] [ [406]Section Contents ] [ [407]Next ] - [ [408]Previous ] + [ [406]Top ] [ [407]Contents ] [ [408]Section Contents ] [ [409]Next ] + [ [410]Previous ] SECTION CONTENTS -3.7.1. [409]Serial Port Configuration -3.7.2. [410]Serial Port Problems -3.7.3. [411]SunLink X.25 -3.7.4. [412]Sun Workstation Keyboard Mapping -3.7.5. [413]Solaris 2.4 and Earlier +3.7.1. [411]Serial Port Configuration +3.7.2. [412]Serial Port Problems +3.7.3. [413]SunLink X.25 +3.7.4. [414]Sun Workstation Keyboard Mapping +3.7.5. [415]Solaris 2.4 and Earlier REFERENCES - * The [414]comp.unix.solaris newsgroup - * [415]http://accesss1.sun.com/ - * [416]http://docs.sun.com/ - * [417]http://www.sunhelp.com/ - * [418]http://www.wins.uva.nl/pub/solaris/solaris2/ - * [419]http://www.wins.uva.nl/cgi-bin/sfaq.cgi - * [420]ftp://ftp.wins.uva.nl/pub/solaris - * [421]http://www.science.uva.nl/pub/solaris/solaris2.html + * The [416]comp.unix.solaris newsgroup + * [417]http://access1.sun.com/ + * [418]http://docs.sun.com/ + * [419]http://www.sunhelp.com/ + * [420]http://www.wins.uva.nl/pub/solaris/solaris2/ + * [421]http://www.wins.uva.nl/cgi-bin/sfaq.cgi + * [422]ftp://ftp.wins.uva.nl/pub/solaris + * [423]http://www.science.uva.nl/pub/solaris/solaris2.html And about serial communications in particular, see "Celeste's Tutorial on Solaris 2.x Modems and Terminals": - [422]http://www.stokely.com/ + [424]http://www.stokely.com/ In particular: - [423]http://www.stokely.com/unix.sysadm.resources/faqs.sun.html + [425]http://www.stokely.com/unix.sysadm.resources/faqs.sun.html For PC-based Solaris, also see general comments on PC-based Unixes in - [424]Section 3.0. Don't expect Solaris or any other kind of Unix to + [426]Section 3.0. Don't expect Solaris or any other kind of Unix to work right on a PC until you resolve all interrupt conflicts. Don't expect to be able to use COM3 or COM4 (or even COM2) until you have configured their addresses and interrupts. 3.7.1. Serial Port Configuration - [ [425]Top ] [ [426]Contents ] [ [427]Section Contents ] [ [428]Section - Contents ] [ [429]Next ] + [ [427]Top ] [ [428]Contents ] [ [429]Section Contents ] [ [430]Section + Contents ] [ [431]Next ] Your serial port can't be used -- or at least won't work right -- until it is enabled in Solaris. For example, you get a message like "SERIAL: @@ -2501,8 +2504,8 @@ $ cat /proc/interrupts 3.7.2. Serial Port Problems - [ [430]Top ] [ [431]Contents ] [ [432]Section Contents ] [ [433]Next ] - [ [434]Previous ] + [ [432]Top ] [ [433]Contents ] [ [434]Section Contents ] [ [435]Next ] + [ [436]Previous ] Current advice from Sun is to always the /dev/cua/x devices for dialing out, rather than the /dev/term/x. Nevertheless, if you have trouble @@ -2515,8 +2518,8 @@ $ cat /proc/interrupts 3.7.3. SunLink X.25 - [ [435]Top ] [ [436]Contents ] [ [437]Section Contents ] [ [438]Next ] - [ [439]Previous ] + [ [437]Top ] [ [438]Contents ] [ [439]Section Contents ] [ [440]Next ] + [ [441]Previous ] The built-in SunLink X.25 support for Solaris 2.3/2.4./25 and SunLink 8.01 or 9.00 works OK provided the X.25 system has been installed and @@ -2556,11 +2559,11 @@ $ cat /proc/interrupts 3.7.4. Sun Workstation Keyboard Mapping - [ [440]Top ] [ [441]Contents ] [ [442]Section Contents ] [ [443]Next ] - [ [444]Previous ] + [ [442]Top ] [ [443]Contents ] [ [444]Section Contents ] [ [445]Next ] + [ [446]Previous ] Hints for using a Sun workstation keyboard for VT emulation when - accesssing VMS, from the [445]comp.os.vms newsgroup: + accessing VMS, from the [447]comp.os.vms newsgroup: From: Jerry Leichter Newsgroups: comp.os.vms @@ -2636,8 +2639,8 @@ $ cat /proc/interrupts 3.7.5. Solaris PPP Connections - [ [446]Top ] [ [447]Contents ] [ [448]Section Contents ] [ [449]Next ] - [ [450]Previous ] + [ [448]Top ] [ [449]Contents ] [ [450]Section Contents ] [ [451]Next ] + [ [452]Previous ] The following is a report from a user of C-Kermit 8.0 on Solaris 8 and 9, who had complained that while Kermit file transfers worked perfectly @@ -2682,8 +2685,8 @@ $ cat /proc/interrupts 3.7.6. Solaris 2.4 and Earlier - [ [451]Top ] [ [452]Contents ] [ [453]Section Contents ] [ - [454]Previous ] + [ [453]Top ] [ [454]Contents ] [ [455]Section Contents ] [ + [456]Previous ] C-Kermit can't be compiled successfully under Solaris 2.3 using SUNWspro cc 2.0.1 unless at least some of the following patches are @@ -2816,22 +2819,22 @@ $ cat /proc/interrupts 3.8. C-KERMIT AND SUNOS - [ [455]Top ] [ [456]Contents ] [ [457]Section Contents ] [ [458]Next ] - [ [459]Previous ] + [ [457]Top ] [ [458]Contents ] [ [459]Section Contents ] [ [460]Next ] + [ [461]Previous ] For additional information, see "Celeste's Tutorial on SunOS 4.1.3+ Modems and Terminals": - [460]http://www.stokely.com/ + [462]http://www.stokely.com/ For FAQs, etc, from Sun, see: - * [461]http://accesss1.sun.com/ + * [463]http://access1.sun.com/ For history of Sun models and SunOS versions, see (should be all the same): - * [462]http://www.ludd.luth.se/~bear/project/sun/sun.hardware.txt - * [463]ftp://ftp.netcom.com/pub/ru/rubicon/sun.hdwr.ref - * [464]ftp://ftp.intnet.net/pub/SUN/Sun-Hardware-Ref + * [464]http://www.ludd.luth.se/~bear/project/sun/sun.hardware.txt + * [465]ftp://ftp.netcom.com/pub/ru/rubicon/sun.hdwr.ref + * [466]ftp://ftp.intnet.net/pub/SUN/Sun-Hardware-Ref Sun SPARCstation users should read the section "Setting up Modem Software" in the Desktop SPARC Sun System & Network Manager's Guide. If @@ -2907,10 +2910,10 @@ $ cat /proc/interrupts 3.9. C-KERMIT AND ULTRIX - [ [465]Top ] [ [466]Contents ] [ [467]Section Contents ] [ [468]Next ] - [ [469]Previous ] + [ [467]Top ] [ [468]Contents ] [ [469]Section Contents ] [ [470]Next ] + [ [471]Previous ] - See also: The [470]comp.unix.ultrix and [471]comp.sys.dec newsgroups. + See also: The [472]comp.unix.ultrix and [473]comp.sys.dec newsgroups. There is no hardware flow control in Ultrix. That's not a Kermit deficiency, but an Ultrix one. @@ -2951,18 +2954,18 @@ $ cat /proc/interrupts 3.10. C-KERMIT AND UNIXWARE - [ [472]Top ] [ [473]Contents ] [ [474]Section Contents ] [ [475]Next ] - [ [476]Previous ] + [ [474]Top ] [ [475]Contents ] [ [476]Section Contents ] [ [477]Next ] + [ [478]Previous ] See also: * The Freebird Project (Unixware software repository) - [477]http://www.freebird.org/ - * The UnixWare FAQ: [478]http://www.freebird.org/faq/ + [479]http://www.freebird.org/ + * The UnixWare FAQ: [480]http://www.freebird.org/faq/ * The following newsgroups: - + [479]comp.unix.unixware.misc - + [480]comp.unix.sco.misc. + + [481]comp.unix.unixware.misc + + [482]comp.unix.sco.misc. - Also see general comments on PC-based Unixes in [481]Section 3.0. By + Also see general comments on PC-based Unixes in [483]Section 3.0. By the way, this section is separate from the SCO (Caldera) section because at the time this section was started, Unixware was owned by a company called Univel. Later it was sold to Novell, and then to SCO. @@ -3000,13 +3003,13 @@ $ cat /proc/interrupts HOWEVER, turning on POSIX features engages all of the "#if (!_POSIX_SOURCE)" clauses in the UnixWare header files, which in turn - prevent us from having modem signals, accesss to the hardware flow + prevent us from having modem signals, access to the hardware flow control APIs, select(), etc -- in short, all the other things we need in communications software, especially when high speeds are used. Oh the irony. And so C-Kermit must be shamelessly butchered -- as it has been so many times before -- to allow us to have the needed features from the POSIX and non-POSIX worlds. See the UNIXWAREPOSIX sections of - [482]ckutio.c. + [484]ckutio.c. After the butchery, we wind up with Unixware 2.x having full modem-signal capability, but politically-correct Unixware 7.x lacking @@ -3064,8 +3067,8 @@ $ cat /proc/interrupts 3.11. C-KERMIT AND APOLLO SR10 - [ [483]Top ] [ [484]Contents ] [ [485]Section Contents ] [ [486]Next ] - [ [487]Previous ] + [ [485]Top ] [ [486]Contents ] [ [487]Section Contents ] [ [488]Next ] + [ [489]Previous ] Reportedly, version 5A(190), when built under Apollo SR10 using "make sr10-bsd", compiles, links, and executes OK, but leaves the terminal @@ -3079,8 +3082,8 @@ $ cat /proc/interrupts 3.12. C-KERMIT AND TANDY XENIX 3.0 - [ [488]Top ] [ [489]Contents ] [ [490]Section Contents ] [ [491]Next ] - [ [492]Previous ] + [ [490]Top ] [ [491]Contents ] [ [492]Section Contents ] [ [493]Next ] + [ [494]Previous ] C-Kermit 7.0 was too big to be built on Tandy Xenix, even in a minimum configuration; version 6.0 is the last one that fits. @@ -3096,8 +3099,8 @@ $ cat /proc/interrupts 3.13. C-KERMIT AND OSF/1 (DIGITAL UNIX) (TRU64 UNIX) - [ [493]Top ] [ [494]Contents ] [ [495]Section Contents ] [ [496]Next ] - [ [497]Previous ] + [ [495]Top ] [ [496]Contents ] [ [497]Section Contents ] [ [498]Next ] + [ [499]Previous ] While putting together and testing C-Kermit 8.0, it was discovered that binaries built for one version of Tru64 Unix (e.g. 4.0G) might exhibit @@ -3137,8 +3140,8 @@ $ cat /proc/interrupts Digital Unix 3.2 evidently wants to believe your terminal is one line longer than you say it is, e.g. when a "more" or "man" command is given. This is has nothing to do with C-Kermit, but tends to annoy - those who use Kermit or other terminal emulators to accesss Digital - Unix systems. Workaround: tell Unix to "stty rows 23" (or whatever). + those who use Kermit or other terminal emulators to access Digital Unix + systems. Workaround: tell Unix to "stty rows 23" (or whatever). Reportedly, there is some bizarre behavior when trying to use a version of C-Kermit built on one Digital Unix 4.0 system on another one, @@ -3159,15 +3162,15 @@ $ cat /proc/interrupts 3.14. C-KERMIT AND SGI IRIX - [ [498]Top ] [ [499]Contents ] [ [500]Section Contents ] [ [501]Next ] - [ [502]Previous ] + [ [500]Top ] [ [501]Contents ] [ [502]Section Contents ] [ [503]Next ] + [ [504]Previous ] See also: - * The [503]comp.sys.sgi.misc and [504]comp.sys.sgi.admin newsgroups. - [505]The SGI website + * The [505]comp.sys.sgi.misc and [506]comp.sys.sgi.admin newsgroups. + [507]The SGI website * The SGI FAQ: - + [506]http://www-viz.tamu.edu/~sgi-faq/ - + [507]ftp://viz.tamu.edu/pub/sgi/faq/ + + [508]http://www-viz.tamu.edu/~sgi-faq/ + + [509]ftp://viz.tamu.edu/pub/sgi/faq/ About IRIX version numbers: "uname -a" tells the "two-digit" version number, such as "5.3" or "6.5". The three-digit form can be seen with @@ -3185,7 +3188,7 @@ $ cat /proc/interrupts MIPS3 R4x00 MIPS4 R5000 and above - Furthermore, there are different Application Binary Inferfaces (ABIs): + Furthermore, there are different Application Binary Interfaces (ABIs): COFF 32 bits, IRIX 5.3, 5.2, 5.1, 4.x and below o32 ELF 32 bits, IRIX 5.3, 6.0 - 6.5 @@ -3244,26 +3247,26 @@ $ cat /proc/interrupts that they do not trap SIGTSTP themselves, so the shell is doing the suspending rather than the application. - Also see notes about IRIX 3.x in the [508]C-Kermit for Unix + Also see notes about IRIX 3.x in the [510]C-Kermit for Unix Installation Instructions. If you have problems making TCP/IP connections in versions of IRIX built with GCC 2.95.2, see the bugs section of: - [509]http://freeware.sgi.com/Installable/gcc-2.95.2.html. + [511]http://freeware.sgi.com/Installable/gcc-2.95.2.html. Reportedly, if you allow gcc to compile C-Kermit on Irix you should be aware that there might be problems with some of the network code. The specifics are at - [510]http://freeware.sgi.com/Installable/gcc-2.95.2.html; scroll down + [512]http://freeware.sgi.com/Installable/gcc-2.95.2.html; scroll down to the "known bugs" section at the end of the document. 3.15. C-KERMIT AND THE BEBOX - [ [511]Top ] [ [512]Contents ] [ [513]Section Contents ] [ [514]Next ] - [ [515]Previous ] + [ [513]Top ] [ [514]Contents ] [ [515]Section Contents ] [ [516]Next ] + [ [517]Previous ] - See also: The [516]comp.sys.be newsgroup. + See also: The [518]comp.sys.be newsgroup. The BeBox has been discontinued and BeOS repositioned for PC platforms. The POSIX parts of BeOS are not finished, nor is the sockets library, @@ -3305,8 +3308,8 @@ $ cat /proc/interrupts 3.16. C-KERMIT AND DG/UX - [ [517]Top ] [ [518]Contents ] [ [519]Section Contents ] [ [520]Next ] - [ [521]Previous ] + [ [519]Top ] [ [520]Contents ] [ [521]Section Contents ] [ [522]Next ] + [ [523]Previous ] Somebody downloaded the C-Kermit 6.0 binary built under DG/UX 5.40 and ran it under DG/UX 5.4R3.10 -- it worked OK except that file dates for @@ -3316,8 +3319,8 @@ $ cat /proc/interrupts 3.17. C-KERMIT AND SEQUENT DYNIX - [ [522]Top ] [ [523]Contents ] [ [524]Section Contents ] [ [525]Next ] - [ [526]Previous ] + [ [524]Top ] [ [525]Contents ] [ [526]Section Contents ] [ [527]Next ] + [ [528]Previous ] Reportedly, when coming into a Sequent Unix (DYNIX) system through an X.25 connection, Kermit doesn't work right because the Sequent's @@ -3329,8 +3332,8 @@ $ cat /proc/interrupts 3.18. C-KERMIT AND FREEBSD, OPENBSD, and NETBSD - [ [527]Top ] [ [528]Contents ] [ [529]Section Contents ] [ [530]Next ] - [ [531]Previous ] + [ [529]Top ] [ [530]Contents ] [ [531]Section Contents ] [ [532]Next ] + [ [533]Previous ] Some NebBSD users have reported difficulty escaping back from CONNECT mode, usually when running NetBSD on non-PC hardware. Probably a @@ -3344,8 +3347,8 @@ $ cat /proc/interrupts 3.19. C-KERMIT AND MAC OS X - [ [532]Top ] [ [533]Contents ] [ [534]Section Contents ] [ [535]Next ] - [ [536]Previous ] + [ [534]Top ] [ [535]Contents ] [ [536]Section Contents ] [ [537]Next ] + [ [538]Previous ] Mac OS X is Apple's 4.4BSD Unix variety, closely related to FreeBSD, but different. "uname -a" is singularly uninformative, as in Linux, @@ -3386,7 +3389,7 @@ $ cat /proc/interrupts I doubt that C-Kermit does anything useful with them. There is no code in C-Kermit for traditional two-forked Macintosh files, but it could be added if there is any demand (code for this existed in - [537]Mac Kermit, the old pre-Mac-OS-X Macintosh version of + [539]Mac Kermit, the old pre-Mac-OS-X Macintosh version of C-Kermit). * In case you want to transfer a traditional Macintosh text file (or data fork of a file that is plain text), you can use these C-Kermit @@ -3401,7 +3404,7 @@ send /text filename * Mac OS X can use a third-party package manager called "fink". Various fink packages for C-Kermit are floating around that are not standard releases. For example, there's a C-Kermit 8.0.201 package - in which C-Kermit was modifed (at least) to use a UUCP lockfile + in which C-Kermit was modified (at least) to use a UUCP lockfile directory that does not exist on vanilla Mac OS X systems. Mac OS X and Serial Ports @@ -3416,7 +3419,7 @@ Mac OS X and Serial Ports equipment, and scientific, medical, and lab equipment (to name a few). Among workers in these areas, there is a need to add serial ports back onto this platform, which is being filled by third-party products such - as the [538]Keyspan High Speed USB Serial Adapter USA-19HS, which has a + as the [540]Keyspan High Speed USB Serial Adapter USA-19HS, which has a DB-9 male connector. To use the Keyspan device, you must install the accompanying device drivers, which winds up giving you serial ports with names like /dev/cu.USA19H3b1P1.1, /dev/cu.KeySerial1, @@ -3431,7 +3434,7 @@ Mac OS X Serial Ports with C-Kermit 8.0 and earlier In earlier versions of C-Kermit, you'll need to either build a special -DNOUUCP version, or deal with the UUCP port contention sytem in - [539]all its glory (this is usually an exercise in futility because any + [541]all its glory (this is usually an exercise in futility because any other applications on your Mac that use the serial port will not necessarily follow the same conventions): @@ -3440,7 +3443,7 @@ Mac OS X Serial Ports with C-Kermit 8.0 and earlier chmod g+w /var/spool/lock chgrp xxxx /dev/cu.* (where xxxx is the name of the group for users to whom serial-port - accesss is to be granted). Use "admin" or other existing group, or + access is to be granted). Use "admin" or other existing group, or create a new group if desired. NB: In the absence of official guidance from Apple or anyone else, we @@ -3448,8 +3451,7 @@ Mac OS X Serial Ports with C-Kermit 8.0 and earlier directory (a) already exists on vanilla Mac OS X installations, and (b) it is the directory used for serial-port lockfiles on many other platforms. - 2. Put all users who need accesss to the serial port in the same - group. + 2. Put all users who need access to the serial port in the same group. 3. Make sure the serial device files that are to be used by C-Kermit have group read-write permission and (if you care) lack world read-write permission, e.g.: @@ -3463,7 +3465,7 @@ chmod 775 wermit mv wermit /usr/local/kermit (or whatever spot is more appropriate, e.g. /usr/bin/). For greater - detail about installation, [540]CLICK HERE. + detail about installation, [542]CLICK HERE. Alternatively, to build a pre-9.0 version of C-Kermit without UUCP lockfile support, set the NOUUCP flag; e.g. (for Mac OS 10.4): @@ -3473,7 +3475,7 @@ mv wermit /usr/local/kermit This circumvents the SET PORT failure "?Access to lockfile directory denied". But it also sacrifices Kermit's ability to ensure that only one copy of Kermit can have the device open at a time, since Mac OS X - is the same as all other varieties of Unix in that exclusive accesss to + is the same as all other varieties of Unix in that exclusive access to serial ports is not enforced in any way. But if it's for your own desktop machine that nobody else uses, a -DNOUUCP version might be adequate and preferable to the alternatives. @@ -3493,7 +3495,7 @@ RS-232 versus RS-422 they do not have enough wires (or more properly in the case RS-422/423, wire pairs) to convey a useful subset of modem signals. - Keyspan also sells a [541]USB Twin Serial Adapter that gives you two + Keyspan also sells a [543]USB Twin Serial Adapter that gives you two Mini-Din8 RS-422 ports, that are no better (or worse) for communicating with modems or serial devices than a real Mac Din-8 port was. In essence, you get Data In, Data Out, and two modem signals. It looks to @@ -3522,16 +3524,16 @@ C-Kermit> connect Instructions for the built-in modem (if any) remain to be written due to lack of knowledge. If you can contribute instructions, hints, or - tips, please [542]send them in. + tips, please [544]send them in. 3.20. C-KERMIT AND COHERENT - [ [543]Top ] [ [544]Contents ] [ [545]Section Contents ] [ - [546]Previous ] + [ [545]Top ] [ [546]Contents ] [ [547]Section Contents ] [ + [548]Previous ] Also see: - [547]http://www.uni-giessen.de/faq/archiv/coherent-faq.general/msg000 + [549]http://www.uni-giessen.de/faq/archiv/coherent-faq.general/msg000 00.html Mark Williams COHERENT was perhaps the first commercial Unix-based @@ -3555,7 +3557,7 @@ C-Kermit> connect 4. GENERAL UNIX-SPECIFIC HINTS, LIMITATIONS, AND BUGS - [ [548]Top ] [ [549]Contents ] [ [550]Next ] [ [551]Previous ] + [ [550]Top ] [ [551]Contents ] [ [552]Next ] [ [553]Previous ] 4.1. Modem Signals @@ -3608,7 +3610,7 @@ C-Kermit> connect switches, such as -x to put it in server mode) into the shell field of the /etc/passwd file. This works pretty well. In some cases, for "ultimate security", you might want to use a version built with - -DNOPUSH (see the [552]Configurations Options document for this, but + -DNOPUSH (see the [554]Configurations Options document for this, but even if you don't, then PUSHing or shelling out from C-Kermit just brings up a new copy of C-Kermit (but warning: this does not prevent the user from explicitly running a shell; e.g. "run /bin/sh"; use @@ -3703,7 +3705,7 @@ C-Kermit> connect platform ranging from very fast to very flow. SSH and PTY commands can fail if (a) all pseudoterminals are in use; or - (b) you do not have read/write accesss to the pseudoterminal that was + (b) you do not have read/write access to the pseudoterminal that was assigned. An example of (b) was reported with the Zipslack Slackware Linux distribution, in which the pseudoterminals were created with crw-r--r-- permission, instead of crw-rw-rw-. @@ -3728,11 +3730,11 @@ C-Kermit> connect 5. INITIALIZATION AND COMMAND FILES - [ [553]Top ] [ [554]Contents ] [ [555]Next ] [ [556]Previous ] + [ [555]Top ] [ [556]Contents ] [ [557]Next ] [ [558]Previous ] C-Kermit's initialization file for Unix is .kermrc (lowercase, starts with period) in your home directory, unless Kermit was built with the - system-wide initialization-file option (see the [557]C-Kermit for Unix + system-wide initialization-file option (see the [559]C-Kermit for Unix Installation Instructions). C-Kermit identifies your home directory based on the environment @@ -3795,7 +3797,7 @@ C-Kermit> connect 6. COMMUNICATION SPEED SELECTION - [ [558]Top ] [ [559]Contents ] [ [560]Next ] [ [561]Previous ] + [ [560]Top ] [ [561]Contents ] [ [562]Next ] [ [563]Previous ] Version-7 based Unix implementations, including 4.3 BSD and earlier and Unix systems based upon BSD, use a 4-bit field to record a serial @@ -3881,12 +3883,12 @@ C-Kermit> connect speed, and then the software must also be told to change to the new, higher speed. - For additional information, read [562]Section 9.5 of the Installation - Instructions, plus any platform-specific notes in [563]Section 3 above. + For additional information, read [564]Section 9.5 of the Installation + Instructions, plus any platform-specific notes in [565]Section 3 above. 7. COMMUNICATIONS AND DIALING - [ [564]Top ] [ [565]Contents ] [ [566]Next ] [ [567]Previous ] + [ [566]Top ] [ [567]Contents ] [ [568]Next ] [ [569]Previous ] 7.1. Serial Ports and Modems @@ -3969,9 +3971,9 @@ C-Kermit> connect 5. If MODEM HANGUP-METHOD is set to RS232-SIGNAL, change it to MODEM-COMMAND. Or vice-versa. 6. Try SET DIAL HANGUP OFF before the DIAL command. Also, SET DIAL - DISPLAY ON to watch what's happening. See [568]Section 8 of the - [569]Installation Instructions. - 7. Read pages 50-67 of [570]Using C-Kermit. + DISPLAY ON to watch what's happening. See [570]Section 8 of the + [571]Installation Instructions. + 7. Read pages 50-67 of [572]Using C-Kermit. 8. As a last resort, don't use the DIAL command at all; SET CARRIER OFF and CONNECT to the modem and dial interactively, or write a script program to dial the modem. @@ -3995,7 +3997,7 @@ C-Kermit> connect 8-bit data and Xon/Xoff flow control at the same time. However, as of edit 174, this code is entirely disabled because it is unreliable: even though the host operating system might (or might not) support LPASS8 - mode correctly, the host accesss protocols (terminal servers, telnet, + mode correctly, the host access protocols (terminal servers, telnet, rlogin, etc) generally have no way of finding out about it and therefore render it ineffective, causing file transfer failures. So as of edit 174, Kermit once again uses rawmode for 8-bit data, and so @@ -4083,7 +4085,7 @@ C-Kermit> connect hang up the connection when your computer drops the DTR signal. So before deciding Kermit doesn't work with your modem, check your modem configuration AND the cable (if any) connecting your modem to the - computer -- it should be a straight-through [571]modem cable conducting + computer -- it should be a straight-through [573]modem cable conducting the signals FG, SG, TD, RD, RTS, CTS, DSR, DTR, CD, and RI. Many Unix systems keep aliases for dialout devices; for example, @@ -4107,7 +4109,7 @@ C-Kermit> connect C-Kermit tries to use the 8th bit for data when parity is NONE, and this generally works on real Unix terminal (tty) devices, but it often - does not work when the Unix system is accesssed over a network via + does not work when the Unix system is accessed over a network via telnet or rlogin protocols, including (in many cases) through terminal servers. For example, an Encore computer with Annex terminal servers only gives a 7-bit path if the rlogin protocol is selected in the @@ -4124,7 +4126,7 @@ C-Kermit> connect 8. HARDWARE FLOW CONTROL - [ [572]Top ] [ [573]Contents ] [ [574]Next ] [ [575]Previous ] + [ [574]Top ] [ [575]Contents ] [ [576]Next ] [ [577]Previous ] SET FLOW RTS/CTS is available in Unix C-Kermit only when the underlying operating system provides an Application Program Interface (API) for @@ -4177,9 +4179,9 @@ C-Kermit> connect 9. TERMINAL CONNECTION AND KEY MAPPING - [ [576]Top ] [ [577]Contents ] [ [578]Next ] [ [579]Previous ] + [ [578]Top ] [ [579]Contents ] [ [580]Next ] [ [581]Previous ] - C-Kermit is not a terminal emulator. Refer to page 147 of [580]Using + C-Kermit is not a terminal emulator. Refer to page 147 of [582]Using C-Kermit, 2nd Edition: "Most versions of C-Kermit -- Unix, VMS, AOS/VS, VOS, etc -- provide terminal connection without emulation. These versions act as a 'semitransparent pipe' between the remote computer @@ -4190,12 +4192,12 @@ C-Kermit> connect If you are an X Windows user, you should be aware of an alternative to xterm that supports VT220 emulation, from Thomas E. Dickey: - [581]http://dickey.his.com/xterm/xterm.html + [583]http://dickey.his.com/xterm/xterm.html Unix C-Kermit's SET KEY command currently can not be used with keys that generate "wide" scan codes or multibyte sequences, such as workstation function or arrow keys, because Unix C-Kermit does not have - direct accesss to the keyboard. + direct access to the keyboard. However, many Unix workstations and/or console drivers provide their own key mapping feature. With xterm, for example, you can use 'xmodmap' @@ -4236,7 +4238,7 @@ C-Kermit> connect 10. FILE TRANSFER - [ [582]Top ] [ [583]Contents ] [ [584]Next ] [ [585]Previous ] + [ [584]Top ] [ [585]Contents ] [ [586]Next ] [ [587]Previous ] On most platforms, C-Kermit can not handle files longer than 2^31 or 2^32 bytes long, because it uses the traditional file i/o APIs that use @@ -4368,12 +4370,12 @@ C-Kermit> connect 11. EXTERNAL FILE TRANSFER PROTOCOLS - [ [586]Top ] [ [587]Contents ] [ [588]Next ] [ [589]Previous ] + [ [588]Top ] [ [589]Contents ] [ [590]Next ] [ [591]Previous ] SECTION CONTENTS - 11.1. [590]C-Kermit as an External Protocol - 11.2. [591]Invoking External Protocols from C-Kermit + 11.1. [592]C-Kermit as an External Protocol + 11.2. [593]Invoking External Protocols from C-Kermit Unix C-Kermit can be used in conjunction with other communications software in various ways. C-Kermit can be invoked from another @@ -4393,9 +4395,9 @@ C-Kermit> connect 11.1. C-KERMIT AS AN EXTERNAL PROTOCOL - [ [592]Top ] [ [593]Contents ] [ [594]Section Contents ] [ [595]Next ] + [ [594]Top ] [ [595]Contents ] [ [596]Section Contents ] [ [597]Next ] - (This section deleted; see [596]Using C-Kermit, 2nd Ed, Chapter 14.) + (This section deleted; see [598]Using C-Kermit, 2nd Ed, Chapter 14.) "pcomm" is a general-purpose terminal program that provides file transfer capabilities itself (X- and YMODEM variations) and the ability @@ -4427,7 +4429,7 @@ C-Kermit> connect Here's another example, for Seyon (a Linux communication program). First try the technique above. If that works, fine; otherwise... If - Seyon does not give you a way to accesss and pass along the file + Seyon does not give you a way to access and pass along the file descriptor, but it starts up the Kermit program with its standard i/o redirected to its (Seyon's) communications file descriptor, you can also experiment with the following method, which worked here in brief @@ -4457,11 +4459,11 @@ C-Kermit> connect 11.2. INVOKING EXTERNAL PROTOCOLS FROM C-KERMIT - [ [597]Top ] [ [598]Contents ] [ [599]Section Contents ] [ - [600]Previous ] + [ [599]Top ] [ [600]Contents ] [ [601]Section Contents ] [ + [602]Previous ] (This section is obsolete, but not totally useless. See Chapter 14 - of [601]Using C-Kermit, 2nd Edition). + of [603]Using C-Kermit, 2nd Edition). After you have opened a communication link with C-Kermit's SET LINE (SET PORT) or SET HOST (TELNET) command, C-Kermit makes its file @@ -4520,15 +4522,15 @@ C-Kermit> connect 12. SECURITY - [ [602]Top ] [ [603]Contents ] [ [604]Next ] [ [605]Previous ] + [ [604]Top ] [ [605]Contents ] [ [606]Next ] [ [607]Previous ] As of version 7.0, C-Kermit supports a wide range of security options for authentication and encryption: Kerberos 4, Kerberos 5 / GSSAPI, - SSL/TLS, and SRP. See the separate [606]security document for details. + SSL/TLS, and SRP. See the separate [608]security document for details. 13. MISCELLANEOUS USER REPORTS - [ [607]Top ] [ [608]Contents ] [ [609]Next ] [ [610]Previous ] + [ [609]Top ] [ [610]Contents ] [ [611]Next ] [ [612]Previous ] Date: Thu, 12 Mar 92 1:59:25 MEZ From: Walter Mecky @@ -4572,7 +4574,7 @@ main() { > You must set line > Not a tty > No more processes. -> One of the following three actions clears the peoblem: +> One of the following three actions clears the problem: > shutdown -y -g0 -i6 > kill -9 the ttymon with the highest PID > Invoke sysadm and disable then enable the line you want to use. @@ -4594,7 +4596,7 @@ main() { We have successfully compiled the above release on a Unisys/Sperry 5000/95. We used the sys5r3 option, rather than sys5r2 since we have - VR3 running on our system. In order to allow dialout accesss to + VR3 running on our system. In order to allow dialout access to non-superusers, we had to do "chmod 666 /dev/tty###, where it had been -rw--w--w- (owned by uucp), and to do "chmod +w /usr/spool/locks". We have done text and binary file transfers through local and remote @@ -4648,7 +4650,7 @@ int argc; char *argv[]; { #ifdef DEBUG fprintf(stderr, "LOCKFILE? %s?\n", lockdev); #endif - if (accesss(lockdev, 00) == 0) { + if (access(lockdev, 00) == 0) { allow=TTY_LOCK; break; } @@ -4683,7 +4685,7 @@ int argc; char *argv[]; { 14. THIRD-PARTY DRIVERS - [ [611]Top ] [ [612]Contents ] [ [613]Next ] [ [614]Previous ] + [ [613]Top ] [ [614]Contents ] [ [615]Next ] [ [616]Previous ] Unix versions, especially those for PCs (SCO, Unixware, etc) might be augmented by third-party communication-board drivers from Digiboard, @@ -4709,7 +4711,7 @@ int argc; char *argv[]; { the rest are supported. This will, as I mentioned earlier, be fixed in the next release of our ATA software." - World Wide Escalation Support, Stallion Technologies, Toowong - QLD, [615]support@stallion.oz.au. + QLD, [617]support@stallion.oz.au. Later (December 1997, from the same source): @@ -4721,15 +4723,15 @@ int argc; char *argv[]; { as the early revision of the EasyIO card and the EasyConnection 8D4 panel, and as always asserted on those cards that do not support the DSR signal in the hardware. The new driver is available from - our Web site, [616]www.stallion.com, in the /drivers/ata5/UnixWare + our Web site, [618]www.stallion.com, in the /drivers/ata5/UnixWare directory. - [ [617]Top ] [ [618]Contents ] [ [619]C-Kermit Home ] [ [620]C-Kermit - 8.0 Overview ] [ [621]Kermit Home ] + [ [619]Top ] [ [620]Contents ] [ [621]C-Kermit Home ] [ [622]C-Kermit + 8.0 Overview ] [ [623]Kermit Home ] __________________________________________________________________ - C-Kermit 8.0 Unix Hints and Tips / [622]The Kermit Project / - [623]Columbia University / [624]kermit@columbia.edu + C-Kermit 8.0 Unix Hints and Tips / [624]The Kermit Project / + [625]Columbia University / [626]kermit@columbia.edu References @@ -4747,613 +4749,615 @@ References 12. http://www.columbia.edu/ 13. http://www.columbia.edu/kermit/ckubwr.html 14. http://www.columbia.edu/kermit/ckdaily.html - 15. http://www.columbia.edu/kermit/ckermit.html - 16. http://www.columbia.edu/kermit/ckuins.html - 17. http://www.columbia.edu/kermit/ckututor.html - 18. http://www.columbia.edu/kermit/ckubwr.html#x1 - 19. http://www.columbia.edu/kermit/ckubwr.html#x2 - 20. http://www.columbia.edu/kermit/ckubwr.html#x3 - 21. http://www.columbia.edu/kermit/ckubwr.html#x4 - 22. http://www.columbia.edu/kermit/ckubwr.html#x5 - 23. http://www.columbia.edu/kermit/ckubwr.html#x6 - 24. http://www.columbia.edu/kermit/ckubwr.html#x7 - 25. http://www.columbia.edu/kermit/ckubwr.html#x8 - 26. http://www.columbia.edu/kermit/ckubwr.html#x9 - 27. http://www.columbia.edu/kermit/ckubwr.html#x10 - 28. http://www.columbia.edu/kermit/ckubwr.html#x11 - 29. http://www.columbia.edu/kermit/ckubwr.html#x12 - 30. http://www.columbia.edu/kermit/ckubwr.html#x13 - 31. http://www.columbia.edu/kermit/ckubwr.html#x14 - 32. http://www.columbia.edu/kermit/ckubwr.html#x3.3 - 33. http://www.columbia.edu/kermit/ckubwr.html#x3.18 - 34. http://www.columbia.edu/kermit/ckubwr.html#x3.19 - 35. http://www.columbia.edu/kermit/ckubwr.html#x3.1 - 36. http://www.columbia.edu/kermit/ckubwr.html#x3.2 - 37. http://www.columbia.edu/kermit/ckubwr.html#x3.7 - 38. http://www.columbia.edu/kermit/ckubwr.html#x3.6 - 39. http://www.columbia.edu/kermit/ckubwr.html#top - 40. http://www.columbia.edu/kermit/ckubwr.html#contents - 41. http://www.columbia.edu/kermit/ckubwr.html#x2 - 42. http://www.columbia.edu/kermit/ckubwr.html#x1.1 - 43. http://www.columbia.edu/kermit/ckubwr.html#x1.2 - 44. http://www.columbia.edu/kermit/ckubwr.html#x1.3 - 45. http://www.columbia.edu/kermit/ckubwr.html#x1.4 - 46. http://www.columbia.edu/kermit/ckubwr.html#x3.3 - 47. http://www.columbia.edu/kermit/ckubwr.html#x3.1 - 48. http://www.columbia.edu/kermit/ckubwr.html#x3.2 - 49. http://www.columbia.edu/kermit/ckubwr.html#x3.7 - 50. http://www.columbia.edu/kermit/ckcbwr.html - 51. mailto:kermit-support@columbia.edu - 52. http://www.columbia.edu/kermit/ckubwr.html#top - 53. http://www.columbia.edu/kermit/ckubwr.html#contents - 54. http://www.columbia.edu/kermit/ckubwr.html#x1.2 - 55. http://www.columbia.edu/kermit/ck60manual.html - 56. http://www.columbia.edu/kermit/ckermit70.html - 57. http://www.columbia.edu/kermit/ckermit80.html - 58. http://www.columbia.edu/kermit/ckermit90.html - 59. http://www.columbia.edu/kermit/ckubwr.html#top - 60. http://www.columbia.edu/kermit/ckubwr.html#contents - 61. http://www.columbia.edu/kermit/ckubwr.html#x1 - 62. http://www.columbia.edu/kermit/ckubwr.html#x1.3 - 63. http://www.columbia.edu/kermit/ckubwr.html#x1.1 - 64. http://www.columbia.edu/kermit/support.html - 65. http://www.columbia.edu/kermit/ckubwr.html#top - 66. http://www.columbia.edu/kermit/ckubwr.html#contents - 67. http://www.columbia.edu/kermit/ckubwr.html#x1 - 68. http://www.columbia.edu/kermit/ckubwr.html#x1.4 - 69. http://www.columbia.edu/kermit/ckubwr.html#x1.2 - 70. http://www.columbia.edu/kermit/ckubwr.html#top - 71. http://www.columbia.edu/kermit/ckubwr.html#contents - 72. http://www.columbia.edu/kermit/ckubwr.html#x1 - 73. http://www.columbia.edu/kermit/ckubwr.html#x1.3 - 74. http://www.columbia.edu/kermit/ckubwr.html#top - 75. http://www.columbia.edu/kermit/ckubwr.html#contents - 76. http://www.columbia.edu/kermit/ckubwr.html#x3 - 77. http://www.columbia.edu/kermit/ckubwr.html#x1 - 78. http://www.columbia.edu/kermit/ckubwr.html#top - 79. http://www.columbia.edu/kermit/ckubwr.html#contents - 80. http://www.columbia.edu/kermit/ckubwr.html#x4 - 81. http://www.columbia.edu/kermit/ckubwr.html#x2 - 82. http://www.columbia.edu/kermit/ckubwr.html#x3.0 - 83. http://www.columbia.edu/kermit/ckubwr.html#x3.1 - 84. http://www.columbia.edu/kermit/ckubwr.html#x3.2 - 85. http://www.columbia.edu/kermit/ckubwr.html#x3.3 - 86. http://www.columbia.edu/kermit/ckubwr.html#x3.4 - 87. http://www.columbia.edu/kermit/ckubwr.html#x3.5 - 88. http://www.columbia.edu/kermit/ckubwr.html#x3.6 - 89. http://www.columbia.edu/kermit/ckubwr.html#x3.7 - 90. http://www.columbia.edu/kermit/ckubwr.html#x3.8 - 91. http://www.columbia.edu/kermit/ckubwr.html#x3.9 - 92. http://www.columbia.edu/kermit/ckubwr.html#x3.10 - 93. http://www.columbia.edu/kermit/ckubwr.html#x3.11 - 94. http://www.columbia.edu/kermit/ckubwr.html#x3.12 - 95. http://www.columbia.edu/kermit/ckubwr.html#x3.13 - 96. http://www.columbia.edu/kermit/ckubwr.html#x3.14 - 97. http://www.columbia.edu/kermit/ckubwr.html#x3.15 - 98. http://www.columbia.edu/kermit/ckubwr.html#x3.16 - 99. http://www.columbia.edu/kermit/ckubwr.html#x3.17 - 100. http://www.columbia.edu/kermit/ckubwr.html#x3.18 - 101. http://www.columbia.edu/kermit/ckubwr.html#x3.19 - 102. http://www.columbia.edu/kermit/ckubwr.html#x3.20 - 103. http://www.faqs.org/ - 104. http://aplawrence.com/Unixart/newtounix.html - 105. http://www.columbia.edu/kermit/ckubwr.html#x3 - 106. mailto:kermit-support@columbia.edu - 107. http://www.columbia.edu/kermit/support.html - 108. http://www.columbia.edu/kermit/ckubwr.html#top - 109. http://www.columbia.edu/kermit/ckubwr.html#contents - 110. http://www.columbia.edu/kermit/ckubwr.html#x3 - 111. http://www.columbia.edu/kermit/ckubwr.html#x3.1 - 112. http://www.pcunix.com/ - 113. http://www.columbia.edu/kermit/ckubwr.html#x3.0.1 - 114. http://www.columbia.edu/kermit/ckubwr.html#x3.0.2 - 115. http://www.columbia.edu/kermit/ckubwr.html#x3.0.3 - 116. http://www.columbia.edu/kermit/ckubwr.html#x3.0.4 - 117. http://www.columbia.edu/kermit/ckubwr.html#x3.0.5 - 118. http://www.columbia.edu/kermit/ckubwr.html#x3.0.6 - 119. http://www.columbia.edu/kermit/ckubwr.html#top - 120. http://www.columbia.edu/kermit/ckubwr.html#contents - 121. http://www.columbia.edu/kermit/ckubwr.html#x3.0 - 122. http://www.columbia.edu/kermit/ckubwr.html#x3.0.2 - 123. http://www.columbia.edu/kermit/ckubwr.html#top - 124. http://www.columbia.edu/kermit/ckubwr.html#contents - 125. http://www.columbia.edu/kermit/ckubwr.html#x3.0 - 126. http://www.columbia.edu/kermit/ckubwr.html#x3.0.3 - 127. http://www.columbia.edu/kermit/ckubwr.html#x3.0.1 - 128. http://www.linmodems.org/ - 129. http://www.microsoft.com/hwdev/platform/PCdesign/LR/default.asp - 130. http://www.columbia.edu/kermit/ckubwr.html#top - 131. http://www.columbia.edu/kermit/ckubwr.html#contents - 132. http://www.columbia.edu/kermit/ckubwr.html#x3.0 - 133. http://www.columbia.edu/kermit/ckubwr.html#x3.0.4 - 134. http://www.columbia.edu/kermit/ckubwr.html#x3.0.2 - 135. http://www.idir.net/~gromitkc/winmodem.html - 136. http://www.digi.com/ - 137. http://www.columbia.edu/kermit/ckubwr.html#top - 138. http://www.columbia.edu/kermit/ckubwr.html#contents - 139. http://www.columbia.edu/kermit/ckubwr.html#x3.0 - 140. http://www.columbia.edu/kermit/ckubwr.html#x3.0.5 - 141. http://www.columbia.edu/kermit/ckubwr.html#x3.0.3 - 142. http://www.columbia.edu/kermit/ckubwr.html#top - 143. http://www.columbia.edu/kermit/ckubwr.html#contents - 144. http://www.columbia.edu/kermit/ckubwr.html#x3.0 - 145. http://www.columbia.edu/kermit/ckubwr.html#x3.0.6 - 146. http://www.columbia.edu/kermit/ckubwr.html#x3.0.4 - 147. http://www.columbia.edu/kermit/ckubwr.html#top - 148. http://www.columbia.edu/kermit/ckubwr.html#contents - 149. http://www.columbia.edu/kermit/ckubwr.html#x3.0 - 150. http://www.columbia.edu/kermit/ckubwr.html#x3.0.5 - 151. http://www.columbia.edu/kermit/ckubwr.html#top - 152. http://www.columbia.edu/kermit/ckubwr.html#contents - 153. http://www.columbia.edu/kermit/ckubwr.html#x3 - 154. http://www.columbia.edu/kermit/ckubwr.html#x3.2 - 155. http://www.columbia.edu/kermit/ckubwr.html#x3.0 - 156. http://www.columbia.edu/kermit/ckubwr.html#x3.1.1 - 157. http://www.columbia.edu/kermit/ckubwr.html#x3.1.2 - 158. http://www.columbia.edu/kermit/ckubwr.html#x3.1.3 - 159. http://www.columbia.edu/kermit/ckubwr.html#x3.1.4 - 160. http://www.columbia.edu/kermit/ckubwr.html#x3.1.5 - 161. http://www.emerson.emory.edu/services/aix-faq/ - 162. http://www.faqs.org/faqs/by-newsgroup/comp/comp.unix.aix.html - 163. http://www.cis.ohio-state.edu/hypertext/faq/usenet/aix-faq/top.html - 164. http://aixpdslib.seas.ucla.edu/ - 165. http://www.rootvg.net(AIXhistory)/ - 166. ftp://rtfm.mit.edu/pub/usenet/news.answers/aix-faq/part1 - 167. ftp://mirrors.aol.com/pub/rtfm/usenet-by-hierarchy/comp/unix/aix - 168. news:comp.unix.aix - 169. http://www.columbia.edu/kermit/ckubwr.html#top - 170. http://www.columbia.edu/kermit/ckubwr.html#contents - 171. http://www.columbia.edu/kermit/ckubwr.html#x3.1 - 172. http://www.columbia.edu/kermit/ckubwr.html#x3.1.2 - 173. http://www.columbia.edu/kermit/ckubwr.html#top - 174. http://www.columbia.edu/kermit/ckubwr.html#contents - 175. http://www.columbia.edu/kermit/ckubwr.html#x3.1 - 176. http://www.columbia.edu/kermit/ckubwr.html#x3.1.3 - 177. http://www.columbia.edu/kermit/ckubwr.html#x3.1.1 - 178. http://www.columbia.edu/kermit/security.html#servers - 179. http://www.columbia.edu/kermit/ckubwr.html#top - 180. http://www.columbia.edu/kermit/ckubwr.html#contents - 181. http://www.columbia.edu/kermit/ckubwr.html#x3.1 - 182. http://www.columbia.edu/kermit/ckubwr.html#x3.1.4 - 183. http://www.columbia.edu/kermit/ckubwr.html#x3.1.2 - 184. http://service.software.ibm.com/rs6000/ - 185. http://www.columbia.edu/kermit/ckubwr.html#top - 186. http://www.columbia.edu/kermit/ckubwr.html#contents - 187. http://www.columbia.edu/kermit/ckubwr.html#x3.1 - 188. http://www.columbia.edu/kermit/ckubwr.html#x3.1.5 - 189. http://www.columbia.edu/kermit/ckubwr.html#x3.1.3 - 190. http://www.columbia.edu/kermit/ckubwr.html#top - 191. http://www.columbia.edu/kermit/ckubwr.html#contents - 192. http://www.columbia.edu/kermit/ckubwr.html#x3.1 - 193. http://www.columbia.edu/kermit/ckubwr.html#x3.1.4 - 194. http://www.columbia.edu/kermit/ckubwr.html#top - 195. http://www.columbia.edu/kermit/ckubwr.html#contents - 196. http://www.columbia.edu/kermit/ckubwr.html#x3 - 197. http://www.columbia.edu/kermit/ckubwr.html#x3.3 - 198. http://www.columbia.edu/kermit/ckubwr.html#x3.1 - 199. http://www.columbia.edu/kermit/ckubwr.html#x3.2.0 - 200. http://www.columbia.edu/kermit/ckubwr.html#x3.2.1 - 201. http://www.columbia.edu/kermit/ckubwr.html#x3.2.2 - 202. http://www.columbia.edu/kermit/ckubwr.html#x3.2.3 - 203. http://www.columbia.edu/kermit/ckubwr.html#x3.2.4 - 204. http://www.columbia.edu/kermit/ckubwr.html#x3.2.5 - 205. news:comp.sys.hp.hpux - 206. http://www.columbia.edu/kermit/ckubwr.html#top - 207. http://www.columbia.edu/kermit/ckubwr.html#contents - 208. http://www.columbia.edu/kermit/ckubwr.html#x3.2 - 209. http://www.columbia.edu/kermit/ckubwr.html#x3.2.1 - 210. http://www.columbia.edu/kermit/ckubwr.html#top - 211. http://www.columbia.edu/kermit/ckubwr.html#contents - 212. http://www.columbia.edu/kermit/ckubwr.html#x3.2 - 213. http://www.columbia.edu/kermit/ckubwr.html#x3.2.2 - 214. http://www.columbia.edu/kermit/ckubwr.html#x3.2.0 - 215. ftp://kermit.columbia.edu/kermit/f/makefile - 216. http://www.columbia.edu/kermit/ckubwr.html#top - 217. http://www.columbia.edu/kermit/ckubwr.html#contents - 218. http://www.columbia.edu/kermit/ckubwr.html#x3.2 - 219. http://www.columbia.edu/kermit/ckubwr.html#x3.2.3 - 220. http://www.columbia.edu/kermit/ckubwr.html#x3.2.1 - 221. http://www.columbia.edu/kermit/ckubwr.html#top - 222. http://www.columbia.edu/kermit/ckubwr.html#contents - 223. http://www.columbia.edu/kermit/ckubwr.html#x3.2 - 224. http://www.columbia.edu/kermit/ckubwr.html#x3.2.4 - 225. http://www.columbia.edu/kermit/ckubwr.html#x3.2.2 - 226. http://www.columbia.edu/kermit/ckubwr.html#x3.2.4.1 - 227. http://www.columbia.edu/kermit/ckubwr.html#x3.2.4.2 - 228. http://www.columbia.edu/kermit/ckubwr.html#x3.2.4.3 - 229. http://www.columbia.edu/kermit/ckubwr.html#x3.2.4.4 - 230. http://www.columbia.edu/kermit/ckubwr.html#x3.2.4.5 - 231. http://www.columbia.edu/kermit/ckubwr.html#top - 232. http://www.columbia.edu/kermit/ckubwr.html#contents - 233. http://www.columbia.edu/kermit/ckubwr.html#x3.2 - 234. http://www.columbia.edu/kermit/ckubwr.html#x3.2.4.2 - 235. http://www.columbia.edu/kermit/ckubwr.html#x3.2.2 - 236. http://www.columbia.edu/kermit/ckubwr.html#top - 237. http://www.columbia.edu/kermit/ckubwr.html#contents - 238. http://www.columbia.edu/kermit/ckubwr.html#x3.2.4 - 239. http://www.columbia.edu/kermit/ckubwr.html#x3.2.4.3 - 240. http://www.columbia.edu/kermit/ckubwr.html#x3.2.4.1 - 241. http://www.columbia.edu/kermit/ckubwr.html#top - 242. http://www.columbia.edu/kermit/ckubwr.html#contents - 243. http://www.columbia.edu/kermit/ckubwr.html#x3.2.4 - 244. http://www.columbia.edu/kermit/ckubwr.html#x3.2.4.4 - 245. http://www.columbia.edu/kermit/ckubwr.html#x3.2.4.2 - 246. http://www.columbia.edu/kermit/ckubwr.html#top - 247. http://www.columbia.edu/kermit/ckubwr.html#contents - 248. http://www.columbia.edu/kermit/ckubwr.html#x3.2.4 - 249. http://www.columbia.edu/kermit/ckubwr.html#x3.2.4.5 - 250. http://www.columbia.edu/kermit/ckubwr.html#x3.2.4.3 - 251. http://www.columbia.edu/kermit/ckubwr.html#top - 252. http://www.columbia.edu/kermit/ckubwr.html#contents - 253. http://www.columbia.edu/kermit/ckubwr.html#x3.2.4 - 254. http://www.columbia.edu/kermit/ckubwr.html#x3.2.4.4 - 255. http://www.columbia.edu/kermit/ckubwr.html#top - 256. http://www.columbia.edu/kermit/ckubwr.html#contents - 257. http://www.columbia.edu/kermit/ckubwr.html#x3.2 - 258. http://www.columbia.edu/kermit/ckubwr.html#x3.2.4 - 259. http://www.columbia.edu/kermit/ckubwr.html#top - 260. http://www.columbia.edu/kermit/ckubwr.html#contents - 261. http://www.columbia.edu/kermit/ckubwr.html#x3 - 262. http://www.columbia.edu/kermit/ckubwr.html#x3.4 - 263. http://www.columbia.edu/kermit/ckubwr.html#x3.2 - 264. http://www.columbia.edu/kermit/ckubwr.html#x3.3.1 - 265. http://www.columbia.edu/kermit/ckubwr.html#x3.3.2 - 266. http://www.columbia.edu/kermit/ckubwr.html#x3.3.3 - 267. http://www.columbia.edu/kermit/ckubwr.html#x3.3.4 - 268. http://www.columbia.edu/kermit/ckubwr.html#x3.3.5 - 269. http://www.columbia.edu/kermit/ckubwr.html#x3.3.6 - 270. http://en.wikipedia.org/wiki/Avahi_(software) - 271. news:comp.os.linux.misc - 272. news:comp.os.linux.answers - 273. http://www.tldp.org/ - 274. http://www.tldp.org/FAQ/Linux-FAQ.html - 275. http://www.tldp.org/HOWTO/Serial-HOWTO.html - 276. http://tldp.org/HOWTO/Modem-HOWTO.html - 277. ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO - 278. ftp://tsx-11.mit.edu/pub/linux/docs/HOWTO - 279. http://www.tldp.org/HOWTO/ - 280. http://www.tldp.org/hmirrors.html - 281. http://www.redhat.com/apps/support/ - 282. http://www.debian.org/support - 283. http://www.slackware.com/support/ - 284. http://www.caldera.com/support/ - 285. http://www.novell.com/support/microsites/microsite.do - 286. http://www.mandrake.com/support/ - 287. http://www.turbolinux.com/support/ - 288. http://www.linmodems.org/ - 289. http://www.columbia.edu/kermit/ckubwr.html#x3.0 - 290. http://linux.dreamtime.org/decnet/ - 291. mailto:kermit-support@columbia.edu - 292. http://www.linmodems.org/ - 293. http://www.columbia.edu/kermit/ckubwr.html#x3.0.2 - 294. http://www.columbia.edu/kermit/security.html#servers - 295. http://www.columbia.edu/kermit/sshclient.html - 296. http://www.columbia.edu/kermit/ckubwr.html#top - 297. http://www.columbia.edu/kermit/ckubwr.html#contents - 298. http://www.columbia.edu/kermit/ckubwr.html#x3 - 299. http://www.columbia.edu/kermit/ckubwr.html#x3.3.2 - 300. http://www.columbia.edu/kermit/ckubwr.html#top - 301. http://www.columbia.edu/kermit/ckubwr.html#contents - 302. http://www.columbia.edu/kermit/ckubwr.html#x3.3 - 303. http://www.columbia.edu/kermit/ckubwr.html#x3.3.3 - 304. http://www.columbia.edu/kermit/ckubwr.html#x3.3.1 - 305. http://www.columbia.edu/kermit/ckubwr.html#x3.0 - 306. http://www.columbia.edu/kermit/ckubwr.html#x6 - 307. http://www.columbia.edu/kermit/ckubwr.html#x7 - 308. http://www.columbia.edu/kermit/ckubwr.html#x8 - 309. http://www.columbia.edu/kermit/ckuins.html#x10 - 310. http://www.columbia.edu/kermit/ckuins.html#x11 - 311. http://www.columbia.edu/kermit/ckuins.html - 312. http://www.columbia.edu/kermit/ckubwr.html#x3.0 - 313. http://linuxwww.db.erau.edu/mail_archives/linux-kernel/Mar_98/1441.html - 314. http://www.columbia.edu/kermit/ckubwr.html#top - 315. http://www.columbia.edu/kermit/ckubwr.html#contents - 316. http://www.columbia.edu/kermit/ckubwr.html#x3.3 - 317. http://www.columbia.edu/kermit/ckubwr.html#x3.3.4 - 318. http://www.columbia.edu/kermit/ckubwr.html#x3.3.2 - 319. http://www.columbia.edu/kermit/ckubwr.html#x3.0.5 - 320. http://www.columbia.edu/kermit/ckfaq.html#term - 321. http://dickey.his.com/xterm/xterm.html - 322. http://dickey.his.com/xterm/xterm.html - 323. ftp://kermit.columbia.edu/kermit/f/xmodmap.txt - 324. http://www.columbia.edu/kermit/ckubwr.html#top - 325. http://www.columbia.edu/kermit/ckubwr.html#contents - 326. http://www.columbia.edu/kermit/ckubwr.html#x3.3 - 327. http://www.columbia.edu/kermit/ckubwr.html#x3.3.5 - 328. http://www.columbia.edu/kermit/ckubwr.html#x3.3.3 - 329. http://www.columbia.edu/kermit/ckubwr.html#top - 330. http://www.columbia.edu/kermit/ckubwr.html#contents - 331. http://www.columbia.edu/kermit/ckubwr.html#x3.3 - 332. http://www.columbia.edu/kermit/ckubwr.html#x3.3.6 - 333. http://www.columbia.edu/kermit/ckubwr.html#x3.3.4 - 334. http://www.columbia.edu/kermit/ckermit.html - 335. mailto:kermit-support@columbia.edu - 336. http://www.redhat.com/support/errata/RHBA-2001-153.html - 337. news:comp.protocols.kermit.misc - 338. http://www.columbia.edu/kermit/ckubwr.html#top - 339. http://www.columbia.edu/kermit/ckubwr.html#contents - 340. http://www.columbia.edu/kermit/ckubwr.html#x3.3 - 341. http://www.columbia.edu/kermit/ckubwr.html#x3.3.5 - 342. http://www.columbia.edu/kermit/ckubwr.html#top - 343. http://www.columbia.edu/kermit/ckubwr.html#contents - 344. http://www.columbia.edu/kermit/ckubwr.html#x3 - 345. http://www.columbia.edu/kermit/ckubwr.html#x3.5 - 346. http://www.columbia.edu/kermit/ckubwr.html#x3.3 - 347. http://www.columbia.edu/kermit/ckubwr.html#top - 348. http://www.columbia.edu/kermit/ckubwr.html#contents - 349. http://www.columbia.edu/kermit/ckubwr.html#x3 - 350. http://www.columbia.edu/kermit/ckubwr.html#x3.6 - 351. http://www.columbia.edu/kermit/ckubwr.html#x3.4 - 352. news:comp.os.qnx - 353. http://www.columbia.edu/kermit/gkermit.html - 354. http://www.columbia.edu/kermit/ckuins.html#x10 - 355. http://www.columbia.edu/kermit/ckuins.html - 356. http://www.columbia.edu/kermit/ckubwr.html#top - 357. http://www.columbia.edu/kermit/ckubwr.html#contents - 358. http://www.columbia.edu/kermit/ckubwr.html#x3 - 359. http://www.columbia.edu/kermit/ckubwr.html#x3.7 - 360. http://www.columbia.edu/kermit/ckubwr.html#x3.5 - 361. http://www.columbia.edu/kermit/ckubwr.html#x3.6.1 - 362. http://www.columbia.edu/kermit/ckubwr.html#x3.6.2 - 363. http://www.columbia.edu/kermit/ckubwr.html#x3.6.3 - 364. http://www.columbia.edu/kermit/ckubwr.html#x3.6.4 - 365. http://www.columbia.edu/kermit/ckubwr.html#x3.10 - 366. http://aplawrence.com/SCOFAQ/ - 367. http://www.zenez.com/cgi-bin/scoprogfaq/faq.pl - 368. http://www.zenez.com/cgi-bin/scouw7faq/faq.pl - 369. http://zenez.pcunix.com/cgi-bin/scouw7faq/faq.pl - 370. http://pcunix.com/Unixart/modems.html - 371. http://www.freebird.org/faq/ - 372. http://www.freebird.org/faq/developer.html - 373. http://support.caldera.com/caldera - 374. http://stage.caldera.com/ta/ - 375. http://aplawrence.com/newtosco.html - 376. http://www.columbia.edu/kermit/ckubwr.html#x3.0.5 - 377. http://www.columbia.edu/kermit/ckfaq.html#term - 378. http://www.columbia.edu/kermit/ckubwr.html#x3.0 - 379. http://www.columbia.edu/kermit/ckubwr.html#top - 380. http://www.columbia.edu/kermit/ckubwr.html#contents - 381. http://www.columbia.edu/kermit/ckubwr.html#x3.6 - 382. http://www.columbia.edu/kermit/ckubwr.html#x3.6.1 - 383. ftp://kermit.columbia.edu/kermit/c-kermit/ckutio.c - 384. http://www.columbia.edu/kermit/ckubwr.html#top - 385. http://www.columbia.edu/kermit/ckubwr.html#contents - 386. http://www.columbia.edu/kermit/ckubwr.html#x3.6 - 387. http://www.columbia.edu/kermit/ckubwr.html#x3.6.3 - 388. http://www.columbia.edu/kermit/ckubwr.html#x3.6.1 - 389. http://www.digi.com/ - 390. ftp://ftp.fu-berlin.de/pub/unix/driver/fas - 391. http://www.columbia.edu/kermit/ckubwr.html#x14 - 392. http://www.sco.com/ - 393. ftp://ftp.sco.com/ - 394. http://www.columbia.edu/kermit/ckubwr.html#top - 395. http://www.columbia.edu/kermit/ckubwr.html#contents - 396. http://www.columbia.edu/kermit/ckubwr.html#x3.6 - 397. http://www.columbia.edu/kermit/ckubwr.html#x3.6.4 - 398. http://www.columbia.edu/kermit/ckubwr.html#x3.6.2 - 399. http://www.columbia.edu/kermit/ckubwr.html#x3.10 - 400. http://www.columbia.edu/kermit/ckubwr.html#top - 401. http://www.columbia.edu/kermit/ckubwr.html#contents - 402. http://www.columbia.edu/kermit/ckubwr.html#x3.6 - 403. http://www.columbia.edu/kermit/ckubwr.html#x3.6.3 - 404. http://www.columbia.edu/kermit/ckubwr.html#top - 405. http://www.columbia.edu/kermit/ckubwr.html#contents - 406. http://www.columbia.edu/kermit/ckubwr.html#x3 - 407. http://www.columbia.edu/kermit/ckubwr.html#x3.8 - 408. http://www.columbia.edu/kermit/ckubwr.html#x3.6 - 409. http://www.columbia.edu/kermit/ckubwr.html#x3.7.1 - 410. http://www.columbia.edu/kermit/ckubwr.html#x3.7.2 - 411. http://www.columbia.edu/kermit/ckubwr.html#x3.7.3 - 412. http://www.columbia.edu/kermit/ckubwr.html#x3.7.4 - 413. http://www.columbia.edu/kermit/ckubwr.html#x3.7.5 - 414. news:comp.unix.solaris - 415. http://accesss1.sun.com/ - 416. http://docs.sun.com/ - 417. http://www.sunhelp.com/ - 418. http://www.wins.uva.nl/pub/solaris/solaris2/ - 419. http://www.wins.uva.nl/cgi-bin/sfaq.cgi - 420. ftp://ftp.wins.uva.nl/pub/solaris - 421. http://www.science.uva.nl/pub/solaris/solaris2.html - 422. http://www.stokely.com/ - 423. http://www.stokely.com/unix.sysadm.resources/faqs.sun.html - 424. http://www.columbia.edu/kermit/ckubwr.html#x3.0 - 425. http://www.columbia.edu/kermit/ckubwr.html#top - 426. http://www.columbia.edu/kermit/ckubwr.html#contents - 427. http://www.columbia.edu/kermit/ckubwr.html#x3 - 428. http://www.columbia.edu/kermit/ckubwr.html#x3.7 - 429. http://www.columbia.edu/kermit/ckubwr.html#x3.7.2 - 430. http://www.columbia.edu/kermit/ckubwr.html#top - 431. http://www.columbia.edu/kermit/ckubwr.html#contents - 432. http://www.columbia.edu/kermit/ckubwr.html#x3.7 - 433. http://www.columbia.edu/kermit/ckubwr.html#x3.7.3 - 434. http://www.columbia.edu/kermit/ckubwr.html#x3.7.1 - 435. http://www.columbia.edu/kermit/ckubwr.html#top - 436. http://www.columbia.edu/kermit/ckubwr.html#contents - 437. http://www.columbia.edu/kermit/ckubwr.html#x3.7 - 438. http://www.columbia.edu/kermit/ckubwr.html#x3.7.4 - 439. http://www.columbia.edu/kermit/ckubwr.html#x3.7.2 - 440. http://www.columbia.edu/kermit/ckubwr.html#top - 441. http://www.columbia.edu/kermit/ckubwr.html#contents - 442. http://www.columbia.edu/kermit/ckubwr.html#x3.7 - 443. http://www.columbia.edu/kermit/ckubwr.html#x3.7.5 - 444. http://www.columbia.edu/kermit/ckubwr.html#x3.7.3 - 445. news:comp.os.vms - 446. http://www.columbia.edu/kermit/ckubwr.html#top - 447. http://www.columbia.edu/kermit/ckubwr.html#contents - 448. http://www.columbia.edu/kermit/ckubwr.html#x3.7 - 449. http://www.columbia.edu/kermit/ckubwr.html#x3.7.6 - 450. http://www.columbia.edu/kermit/ckubwr.html#x3.7.4 - 451. http://www.columbia.edu/kermit/ckubwr.html#top - 452. http://www.columbia.edu/kermit/ckubwr.html#contents - 453. http://www.columbia.edu/kermit/ckubwr.html#x3.7 - 454. http://www.columbia.edu/kermit/ckubwr.html#x3.7.5 - 455. http://www.columbia.edu/kermit/ckubwr.html#top - 456. http://www.columbia.edu/kermit/ckubwr.html#contents - 457. http://www.columbia.edu/kermit/ckubwr.html#x3 - 458. http://www.columbia.edu/kermit/ckubwr.html#x3.9 - 459. http://www.columbia.edu/kermit/ckubwr.html#x3.7 - 460. http://www.stokely.com/ - 461. http://accesss1.sun.com/ - 462. http://www.ludd.luth.se/~bear/project/sun/sun.hardware.txt - 463. ftp://ftp.netcom.com/pub/ru/rubicon/sun.hdwr.ref - 464. ftp://ftp.intnet.net/pub/SUN/Sun-Hardware-Ref - 465. http://www.columbia.edu/kermit/ckubwr.html#top - 466. http://www.columbia.edu/kermit/ckubwr.html#contents - 467. http://www.columbia.edu/kermit/ckubwr.html#x3 - 468. http://www.columbia.edu/kermit/ckubwr.html#x3.10 - 469. http://www.columbia.edu/kermit/ckubwr.html#x3.8 - 470. news:comp.unix.ultrix - 471. news:comp.sys.dec - 472. http://www.columbia.edu/kermit/ckubwr.html#top - 473. http://www.columbia.edu/kermit/ckubwr.html#contents - 474. http://www.columbia.edu/kermit/ckubwr.html#x3 - 475. http://www.columbia.edu/kermit/ckubwr.html#x3.11 - 476. http://www.columbia.edu/kermit/ckubwr.html#x3.9 - 477. http://www.freebird.org/ - 478. http://www.freebird.org/faq/ - 479. news:comp.unix.unixware.misc - 480. news:comp.unix.sco.misc - 481. http://www.columbia.edu/kermit/ckubwr.html#x3.0 - 482. ftp://kermit.columbia.edu/kermit/f/ckutio.c - 483. http://www.columbia.edu/kermit/ckubwr.html#top - 484. http://www.columbia.edu/kermit/ckubwr.html#contents - 485. http://www.columbia.edu/kermit/ckubwr.html#x3 - 486. http://www.columbia.edu/kermit/ckubwr.html#x3.12 - 487. http://www.columbia.edu/kermit/ckubwr.html#x3.10 - 488. http://www.columbia.edu/kermit/ckubwr.html#top - 489. http://www.columbia.edu/kermit/ckubwr.html#contents - 490. http://www.columbia.edu/kermit/ckubwr.html#x3 - 491. http://www.columbia.edu/kermit/ckubwr.html#x3.13 - 492. http://www.columbia.edu/kermit/ckubwr.html#x3.11 - 493. http://www.columbia.edu/kermit/ckubwr.html#top - 494. http://www.columbia.edu/kermit/ckubwr.html#contents - 495. http://www.columbia.edu/kermit/ckubwr.html#x3 - 496. http://www.columbia.edu/kermit/ckubwr.html#x3.14 - 497. http://www.columbia.edu/kermit/ckubwr.html#x3.12 - 498. http://www.columbia.edu/kermit/ckubwr.html#top - 499. http://www.columbia.edu/kermit/ckubwr.html#contents - 500. http://www.columbia.edu/kermit/ckubwr.html#x3 - 501. http://www.columbia.edu/kermit/ckubwr.html#x3.15 - 502. http://www.columbia.edu/kermit/ckubwr.html#x3.13 - 503. news:comp.sys.sgi.misc - 504. news:comp.sys.sgi.admin - 505. http://www.sgi.com/ - 506. http://www-viz.tamu.edu/~sgi-faq/ - 507. ftp://viz.tamu.edu/pub/sgi/faq/ - 508. http://www.columbia.edu/kermit/ckuins.html - 509. http://freeware.sgi.com/Installable/gcc-2.95.2.html - 510. http://freeware.sgi.com/Installable/gcc-2.95.2.html - 511. http://www.columbia.edu/kermit/ckubwr.html#top - 512. http://www.columbia.edu/kermit/ckubwr.html#contents - 513. http://www.columbia.edu/kermit/ckubwr.html#x3 - 514. http://www.columbia.edu/kermit/ckubwr.html#x3.16 - 515. http://www.columbia.edu/kermit/ckubwr.html#x3.14 - 516. news:comp.sys.be - 517. http://www.columbia.edu/kermit/ckubwr.html#top - 518. http://www.columbia.edu/kermit/ckubwr.html#contents - 519. http://www.columbia.edu/kermit/ckubwr.html#x3 - 520. http://www.columbia.edu/kermit/ckubwr.html#x3.17 - 521. http://www.columbia.edu/kermit/ckubwr.html#x3.15 - 522. http://www.columbia.edu/kermit/ckubwr.html#top - 523. http://www.columbia.edu/kermit/ckubwr.html#contents - 524. http://www.columbia.edu/kermit/ckubwr.html#x3 - 525. http://www.columbia.edu/kermit/ckubwr.html#x3.18 - 526. http://www.columbia.edu/kermit/ckubwr.html#x3.16 - 527. http://www.columbia.edu/kermit/ckubwr.html#top - 528. http://www.columbia.edu/kermit/ckubwr.html#contents - 529. http://www.columbia.edu/kermit/ckubwr.html#x3 - 530. http://www.columbia.edu/kermit/ckubwr.html#x3.19 - 531. http://www.columbia.edu/kermit/ckubwr.html#x3.17 - 532. http://www.columbia.edu/kermit/ckubwr.html#top - 533. http://www.columbia.edu/kermit/ckubwr.html#contents - 534. http://www.columbia.edu/kermit/ckubwr.html#x3 - 535. http://www.columbia.edu/kermit/ckubwr.html#x3.20 - 536. http://www.columbia.edu/kermit/ckubwr.html#x3.18 - 537. http://www.columbia.edu/kermit/mac.html - 538. http://www.amazon.com/gp/product/B0000VYJRY?ie=UTF8&tag=aleidmoreldom-20&linkCode=as2&camp=1789&creative=390957&creativeASIN=B0000VYJRY - 539. http://www.columbia.edu/kermit/ckuins.html#x10 - 540. http://www.columbia.edu/kermit/ckuins.html - 541. http://www.amazon.com/gp/product/B000FX61MS?ie=UTF8&tag=aleidmoreldom-20&linkCode=as2&camp=1789&creative=390957&creativeASIN=B000FX61MS - 542. mailto:kermit@columbia.edu - 543. http://www.columbia.edu/kermit/ckubwr.html#top - 544. http://www.columbia.edu/kermit/ckubwr.html#contents - 545. http://www.columbia.edu/kermit/ckubwr.html#x3 - 546. http://www.columbia.edu/kermit/ckubwr.html#x3.19 - 547. http://www.uni-giessen.de/faq/archiv/coherent-faq.general/msg00000.html - 548. http://www.columbia.edu/kermit/ckubwr.html#top - 549. http://www.columbia.edu/kermit/ckubwr.html#contents - 550. http://www.columbia.edu/kermit/ckubwr.html#x5 - 551. http://www.columbia.edu/kermit/ckubwr.html#x3 - 552. http://www.columbia.edu/kermit/ckccfg.html - 553. http://www.columbia.edu/kermit/ckubwr.html#top - 554. http://www.columbia.edu/kermit/ckubwr.html#contents - 555. http://www.columbia.edu/kermit/ckubwr.html#x6 - 556. http://www.columbia.edu/kermit/ckubwr.html#x4 - 557. http://www.columbia.edu/kermit/ckuins.html - 558. http://www.columbia.edu/kermit/ckubwr.html#top - 559. http://www.columbia.edu/kermit/ckubwr.html#contents - 560. http://www.columbia.edu/kermit/ckubwr.html#x7 - 561. http://www.columbia.edu/kermit/ckubwr.html#x5 - 562. http://www.columbia.edu/kermit/ckuins.html#9.5 - 563. http://www.columbia.edu/kermit/ckubwr.html#x3 - 564. http://www.columbia.edu/kermit/ckubwr.html#top - 565. http://www.columbia.edu/kermit/ckubwr.html#contents - 566. http://www.columbia.edu/kermit/ckubwr.html#x8 - 567. http://www.columbia.edu/kermit/ckubwr.html#x6 - 568. http://www.columbia.edu/kermit/ckuins.html#x8 - 569. http://www.columbia.edu/kermit/ckuins.html - 570. http://www.columbia.edu/kermit/ck60manual.html - 571. http://www.columbia.edu/kermit/cable.html - 572. http://www.columbia.edu/kermit/ckubwr.html#top - 573. http://www.columbia.edu/kermit/ckubwr.html#contents - 574. http://www.columbia.edu/kermit/ckubwr.html#x9 - 575. http://www.columbia.edu/kermit/ckubwr.html#x7 - 576. http://www.columbia.edu/kermit/ckubwr.html#top - 577. http://www.columbia.edu/kermit/ckubwr.html#contents - 578. http://www.columbia.edu/kermit/ckubwr.html#x10 - 579. http://www.columbia.edu/kermit/ckubwr.html#x8 - 580. http://www.columbia.edu/kermit/ck60manual.html - 581. http://dickey.his.com/xterm/xterm.html - 582. http://www.columbia.edu/kermit/ckubwr.html#top - 583. http://www.columbia.edu/kermit/ckubwr.html#contents - 584. http://www.columbia.edu/kermit/ckubwr.html#x11 - 585. http://www.columbia.edu/kermit/ckubwr.html#x9 - 586. http://www.columbia.edu/kermit/ckubwr.html#top - 587. http://www.columbia.edu/kermit/ckubwr.html#contents - 588. http://www.columbia.edu/kermit/ckubwr.html#x12 - 589. http://www.columbia.edu/kermit/ckubwr.html#x10 - 590. http://www.columbia.edu/kermit/ckubwr.html#x11.1 - 591. http://www.columbia.edu/kermit/ckubwr.html#x11.2 - 592. http://www.columbia.edu/kermit/ckubwr.html#top - 593. http://www.columbia.edu/kermit/ckubwr.html#contents - 594. http://www.columbia.edu/kermit/ckubwr.html#x11 - 595. http://www.columbia.edu/kermit/ckubwr.html#x11.2 - 596. http://www.columbia.edu/kermit/ck60manual.html - 597. http://www.columbia.edu/kermit/ckubwr.html#top - 598. http://www.columbia.edu/kermit/ckubwr.html#contents - 599. http://www.columbia.edu/kermit/ckubwr.html#x11 - 600. http://www.columbia.edu/kermit/ckubwr.html#x11.1 - 601. http://www.columbia.edu/kermit/ck60manual.html - 602. http://www.columbia.edu/kermit/ckubwr.html#top - 603. http://www.columbia.edu/kermit/ckubwr.html#contents - 604. http://www.columbia.edu/kermit/ckubwr.html#x13 - 605. http://www.columbia.edu/kermit/ckubwr.html#x11 - 606. http://www.columbia.edu/kermit/security.html - 607. http://www.columbia.edu/kermit/ckubwr.html#top - 608. http://www.columbia.edu/kermit/ckubwr.html#contents - 609. http://www.columbia.edu/kermit/ckubwr.html#x14 - 610. http://www.columbia.edu/kermit/ckubwr.html#x12 - 611. http://www.columbia.edu/kermit/ckubwr.html#top - 612. http://www.columbia.edu/kermit/ckubwr.html#contents - 613. http://www.columbia.edu/kermit/ckubwr.html#x15 - 614. http://www.columbia.edu/kermit/ckubwr.html#x14 - 615. mailto:support@stallion.oz.au - 616. http://www.stallion.com/ - 617. http://www.columbia.edu/kermit/ckubwr.html#top - 618. http://www.columbia.edu/kermit/ckubwr.html#contents - 619. http://www.columbia.edu/kermit/ckermit.html - 620. http://www.columbia.edu/kermit/ck80.html - 621. http://www.columbia.edu/kermit/index.html - 622. http://www.columbia.edu/kermit/index.html - 623. http://www.columbia.edu/ - 624. mailto:kermit@columbia.edu + 15. http://www.columbia.edu/kermit/ckdaily.html + 16. http://www.columbia.edu/kermit/ckdaily.html + 17. http://www.columbia.edu/kermit/ckermit.html + 18. http://www.columbia.edu/kermit/ckuins.html + 19. http://www.columbia.edu/kermit/ckututor.html + 20. http://www.columbia.edu/kermit/ckubwr.html#x1 + 21. http://www.columbia.edu/kermit/ckubwr.html#x2 + 22. http://www.columbia.edu/kermit/ckubwr.html#x3 + 23. http://www.columbia.edu/kermit/ckubwr.html#x4 + 24. http://www.columbia.edu/kermit/ckubwr.html#x5 + 25. http://www.columbia.edu/kermit/ckubwr.html#x6 + 26. http://www.columbia.edu/kermit/ckubwr.html#x7 + 27. http://www.columbia.edu/kermit/ckubwr.html#x8 + 28. http://www.columbia.edu/kermit/ckubwr.html#x9 + 29. http://www.columbia.edu/kermit/ckubwr.html#x10 + 30. http://www.columbia.edu/kermit/ckubwr.html#x11 + 31. http://www.columbia.edu/kermit/ckubwr.html#x12 + 32. http://www.columbia.edu/kermit/ckubwr.html#x13 + 33. http://www.columbia.edu/kermit/ckubwr.html#x14 + 34. http://www.columbia.edu/kermit/ckubwr.html#x3.3 + 35. http://www.columbia.edu/kermit/ckubwr.html#x3.18 + 36. http://www.columbia.edu/kermit/ckubwr.html#x3.19 + 37. http://www.columbia.edu/kermit/ckubwr.html#x3.1 + 38. http://www.columbia.edu/kermit/ckubwr.html#x3.2 + 39. http://www.columbia.edu/kermit/ckubwr.html#x3.7 + 40. http://www.columbia.edu/kermit/ckubwr.html#x3.6 + 41. http://www.columbia.edu/kermit/ckubwr.html#top + 42. http://www.columbia.edu/kermit/ckubwr.html#contents + 43. http://www.columbia.edu/kermit/ckubwr.html#x2 + 44. http://www.columbia.edu/kermit/ckubwr.html#x1.1 + 45. http://www.columbia.edu/kermit/ckubwr.html#x1.2 + 46. http://www.columbia.edu/kermit/ckubwr.html#x1.3 + 47. http://www.columbia.edu/kermit/ckubwr.html#x1.4 + 48. http://www.columbia.edu/kermit/ckubwr.html#x3.3 + 49. http://www.columbia.edu/kermit/ckubwr.html#x3.1 + 50. http://www.columbia.edu/kermit/ckubwr.html#x3.2 + 51. http://www.columbia.edu/kermit/ckubwr.html#x3.7 + 52. http://www.columbia.edu/kermit/ckcbwr.html + 53. mailto:kermit-support@columbia.edu + 54. http://www.columbia.edu/kermit/ckubwr.html#top + 55. http://www.columbia.edu/kermit/ckubwr.html#contents + 56. http://www.columbia.edu/kermit/ckubwr.html#x1.2 + 57. http://www.columbia.edu/kermit/ck60manual.html + 58. http://www.columbia.edu/kermit/ckermit70.html + 59. http://www.columbia.edu/kermit/ckermit80.html + 60. http://www.columbia.edu/kermit/ckermit90.html + 61. http://www.columbia.edu/kermit/ckubwr.html#top + 62. http://www.columbia.edu/kermit/ckubwr.html#contents + 63. http://www.columbia.edu/kermit/ckubwr.html#x1 + 64. http://www.columbia.edu/kermit/ckubwr.html#x1.3 + 65. http://www.columbia.edu/kermit/ckubwr.html#x1.1 + 66. http://www.columbia.edu/kermit/support.html + 67. http://www.columbia.edu/kermit/ckubwr.html#top + 68. http://www.columbia.edu/kermit/ckubwr.html#contents + 69. http://www.columbia.edu/kermit/ckubwr.html#x1 + 70. http://www.columbia.edu/kermit/ckubwr.html#x1.4 + 71. http://www.columbia.edu/kermit/ckubwr.html#x1.2 + 72. http://www.columbia.edu/kermit/ckubwr.html#top + 73. http://www.columbia.edu/kermit/ckubwr.html#contents + 74. http://www.columbia.edu/kermit/ckubwr.html#x1 + 75. http://www.columbia.edu/kermit/ckubwr.html#x1.3 + 76. http://www.columbia.edu/kermit/ckubwr.html#top + 77. http://www.columbia.edu/kermit/ckubwr.html#contents + 78. http://www.columbia.edu/kermit/ckubwr.html#x3 + 79. http://www.columbia.edu/kermit/ckubwr.html#x1 + 80. http://www.columbia.edu/kermit/ckubwr.html#top + 81. http://www.columbia.edu/kermit/ckubwr.html#contents + 82. http://www.columbia.edu/kermit/ckubwr.html#x4 + 83. http://www.columbia.edu/kermit/ckubwr.html#x2 + 84. http://www.columbia.edu/kermit/ckubwr.html#x3.0 + 85. http://www.columbia.edu/kermit/ckubwr.html#x3.1 + 86. http://www.columbia.edu/kermit/ckubwr.html#x3.2 + 87. http://www.columbia.edu/kermit/ckubwr.html#x3.3 + 88. http://www.columbia.edu/kermit/ckubwr.html#x3.4 + 89. http://www.columbia.edu/kermit/ckubwr.html#x3.5 + 90. http://www.columbia.edu/kermit/ckubwr.html#x3.6 + 91. http://www.columbia.edu/kermit/ckubwr.html#x3.7 + 92. http://www.columbia.edu/kermit/ckubwr.html#x3.8 + 93. http://www.columbia.edu/kermit/ckubwr.html#x3.9 + 94. http://www.columbia.edu/kermit/ckubwr.html#x3.10 + 95. http://www.columbia.edu/kermit/ckubwr.html#x3.11 + 96. http://www.columbia.edu/kermit/ckubwr.html#x3.12 + 97. http://www.columbia.edu/kermit/ckubwr.html#x3.13 + 98. http://www.columbia.edu/kermit/ckubwr.html#x3.14 + 99. http://www.columbia.edu/kermit/ckubwr.html#x3.15 + 100. http://www.columbia.edu/kermit/ckubwr.html#x3.16 + 101. http://www.columbia.edu/kermit/ckubwr.html#x3.17 + 102. http://www.columbia.edu/kermit/ckubwr.html#x3.18 + 103. http://www.columbia.edu/kermit/ckubwr.html#x3.19 + 104. http://www.columbia.edu/kermit/ckubwr.html#x3.20 + 105. http://www.faqs.org/ + 106. http://aplawrence.com/Unixart/newtounix.html + 107. http://www.columbia.edu/kermit/ckubwr.html#x3 + 108. mailto:kermit-support@columbia.edu + 109. http://www.columbia.edu/kermit/support.html + 110. http://www.columbia.edu/kermit/ckubwr.html#top + 111. http://www.columbia.edu/kermit/ckubwr.html#contents + 112. http://www.columbia.edu/kermit/ckubwr.html#x3 + 113. http://www.columbia.edu/kermit/ckubwr.html#x3.1 + 114. http://www.pcunix.com/ + 115. http://www.columbia.edu/kermit/ckubwr.html#x3.0.1 + 116. http://www.columbia.edu/kermit/ckubwr.html#x3.0.2 + 117. http://www.columbia.edu/kermit/ckubwr.html#x3.0.3 + 118. http://www.columbia.edu/kermit/ckubwr.html#x3.0.4 + 119. http://www.columbia.edu/kermit/ckubwr.html#x3.0.5 + 120. http://www.columbia.edu/kermit/ckubwr.html#x3.0.6 + 121. http://www.columbia.edu/kermit/ckubwr.html#top + 122. http://www.columbia.edu/kermit/ckubwr.html#contents + 123. http://www.columbia.edu/kermit/ckubwr.html#x3.0 + 124. http://www.columbia.edu/kermit/ckubwr.html#x3.0.2 + 125. http://www.columbia.edu/kermit/ckubwr.html#top + 126. http://www.columbia.edu/kermit/ckubwr.html#contents + 127. http://www.columbia.edu/kermit/ckubwr.html#x3.0 + 128. http://www.columbia.edu/kermit/ckubwr.html#x3.0.3 + 129. http://www.columbia.edu/kermit/ckubwr.html#x3.0.1 + 130. http://www.linmodems.org/ + 131. http://www.microsoft.com/hwdev/platform/PCdesign/LR/default.asp + 132. http://www.columbia.edu/kermit/ckubwr.html#top + 133. http://www.columbia.edu/kermit/ckubwr.html#contents + 134. http://www.columbia.edu/kermit/ckubwr.html#x3.0 + 135. http://www.columbia.edu/kermit/ckubwr.html#x3.0.4 + 136. http://www.columbia.edu/kermit/ckubwr.html#x3.0.2 + 137. http://www.idir.net/~gromitkc/winmodem.html + 138. http://www.digi.com/ + 139. http://www.columbia.edu/kermit/ckubwr.html#top + 140. http://www.columbia.edu/kermit/ckubwr.html#contents + 141. http://www.columbia.edu/kermit/ckubwr.html#x3.0 + 142. http://www.columbia.edu/kermit/ckubwr.html#x3.0.5 + 143. http://www.columbia.edu/kermit/ckubwr.html#x3.0.3 + 144. http://www.columbia.edu/kermit/ckubwr.html#top + 145. http://www.columbia.edu/kermit/ckubwr.html#contents + 146. http://www.columbia.edu/kermit/ckubwr.html#x3.0 + 147. http://www.columbia.edu/kermit/ckubwr.html#x3.0.6 + 148. http://www.columbia.edu/kermit/ckubwr.html#x3.0.4 + 149. http://www.columbia.edu/kermit/ckubwr.html#top + 150. http://www.columbia.edu/kermit/ckubwr.html#contents + 151. http://www.columbia.edu/kermit/ckubwr.html#x3.0 + 152. http://www.columbia.edu/kermit/ckubwr.html#x3.0.5 + 153. http://www.columbia.edu/kermit/ckubwr.html#top + 154. http://www.columbia.edu/kermit/ckubwr.html#contents + 155. http://www.columbia.edu/kermit/ckubwr.html#x3 + 156. http://www.columbia.edu/kermit/ckubwr.html#x3.2 + 157. http://www.columbia.edu/kermit/ckubwr.html#x3.0 + 158. http://www.columbia.edu/kermit/ckubwr.html#x3.1.1 + 159. http://www.columbia.edu/kermit/ckubwr.html#x3.1.2 + 160. http://www.columbia.edu/kermit/ckubwr.html#x3.1.3 + 161. http://www.columbia.edu/kermit/ckubwr.html#x3.1.4 + 162. http://www.columbia.edu/kermit/ckubwr.html#x3.1.5 + 163. http://www.emerson.emory.edu/services/aix-faq/ + 164. http://www.faqs.org/faqs/by-newsgroup/comp/comp.unix.aix.html + 165. http://www.cis.ohio-state.edu/hypertext/faq/usenet/aix-faq/top.html + 166. http://aixpdslib.seas.ucla.edu/ + 167. http://www.rootvg.net(AIXhistory)/ + 168. ftp://rtfm.mit.edu/pub/usenet/news.answers/aix-faq/part1 + 169. ftp://mirrors.aol.com/pub/rtfm/usenet-by-hierarchy/comp/unix/aix + 170. news:comp.unix.aix + 171. http://www.columbia.edu/kermit/ckubwr.html#top + 172. http://www.columbia.edu/kermit/ckubwr.html#contents + 173. http://www.columbia.edu/kermit/ckubwr.html#x3.1 + 174. http://www.columbia.edu/kermit/ckubwr.html#x3.1.2 + 175. http://www.columbia.edu/kermit/ckubwr.html#top + 176. http://www.columbia.edu/kermit/ckubwr.html#contents + 177. http://www.columbia.edu/kermit/ckubwr.html#x3.1 + 178. http://www.columbia.edu/kermit/ckubwr.html#x3.1.3 + 179. http://www.columbia.edu/kermit/ckubwr.html#x3.1.1 + 180. http://www.columbia.edu/kermit/security.html#servers + 181. http://www.columbia.edu/kermit/ckubwr.html#top + 182. http://www.columbia.edu/kermit/ckubwr.html#contents + 183. http://www.columbia.edu/kermit/ckubwr.html#x3.1 + 184. http://www.columbia.edu/kermit/ckubwr.html#x3.1.4 + 185. http://www.columbia.edu/kermit/ckubwr.html#x3.1.2 + 186. http://service.software.ibm.com/rs6000/ + 187. http://www.columbia.edu/kermit/ckubwr.html#top + 188. http://www.columbia.edu/kermit/ckubwr.html#contents + 189. http://www.columbia.edu/kermit/ckubwr.html#x3.1 + 190. http://www.columbia.edu/kermit/ckubwr.html#x3.1.5 + 191. http://www.columbia.edu/kermit/ckubwr.html#x3.1.3 + 192. http://www.columbia.edu/kermit/ckubwr.html#top + 193. http://www.columbia.edu/kermit/ckubwr.html#contents + 194. http://www.columbia.edu/kermit/ckubwr.html#x3.1 + 195. http://www.columbia.edu/kermit/ckubwr.html#x3.1.4 + 196. http://www.columbia.edu/kermit/ckubwr.html#top + 197. http://www.columbia.edu/kermit/ckubwr.html#contents + 198. http://www.columbia.edu/kermit/ckubwr.html#x3 + 199. http://www.columbia.edu/kermit/ckubwr.html#x3.3 + 200. http://www.columbia.edu/kermit/ckubwr.html#x3.1 + 201. http://www.columbia.edu/kermit/ckubwr.html#x3.2.0 + 202. http://www.columbia.edu/kermit/ckubwr.html#x3.2.1 + 203. http://www.columbia.edu/kermit/ckubwr.html#x3.2.2 + 204. http://www.columbia.edu/kermit/ckubwr.html#x3.2.3 + 205. http://www.columbia.edu/kermit/ckubwr.html#x3.2.4 + 206. http://www.columbia.edu/kermit/ckubwr.html#x3.2.5 + 207. news:comp.sys.hp.hpux + 208. http://www.columbia.edu/kermit/ckubwr.html#top + 209. http://www.columbia.edu/kermit/ckubwr.html#contents + 210. http://www.columbia.edu/kermit/ckubwr.html#x3.2 + 211. http://www.columbia.edu/kermit/ckubwr.html#x3.2.1 + 212. http://www.columbia.edu/kermit/ckubwr.html#top + 213. http://www.columbia.edu/kermit/ckubwr.html#contents + 214. http://www.columbia.edu/kermit/ckubwr.html#x3.2 + 215. http://www.columbia.edu/kermit/ckubwr.html#x3.2.2 + 216. http://www.columbia.edu/kermit/ckubwr.html#x3.2.0 + 217. ftp://kermit.columbia.edu/kermit/f/makefile + 218. http://www.columbia.edu/kermit/ckubwr.html#top + 219. http://www.columbia.edu/kermit/ckubwr.html#contents + 220. http://www.columbia.edu/kermit/ckubwr.html#x3.2 + 221. http://www.columbia.edu/kermit/ckubwr.html#x3.2.3 + 222. http://www.columbia.edu/kermit/ckubwr.html#x3.2.1 + 223. http://www.columbia.edu/kermit/ckubwr.html#top + 224. http://www.columbia.edu/kermit/ckubwr.html#contents + 225. http://www.columbia.edu/kermit/ckubwr.html#x3.2 + 226. http://www.columbia.edu/kermit/ckubwr.html#x3.2.4 + 227. http://www.columbia.edu/kermit/ckubwr.html#x3.2.2 + 228. http://www.columbia.edu/kermit/ckubwr.html#x3.2.4.1 + 229. http://www.columbia.edu/kermit/ckubwr.html#x3.2.4.2 + 230. http://www.columbia.edu/kermit/ckubwr.html#x3.2.4.3 + 231. http://www.columbia.edu/kermit/ckubwr.html#x3.2.4.4 + 232. http://www.columbia.edu/kermit/ckubwr.html#x3.2.4.5 + 233. http://www.columbia.edu/kermit/ckubwr.html#top + 234. http://www.columbia.edu/kermit/ckubwr.html#contents + 235. http://www.columbia.edu/kermit/ckubwr.html#x3.2 + 236. http://www.columbia.edu/kermit/ckubwr.html#x3.2.4.2 + 237. http://www.columbia.edu/kermit/ckubwr.html#x3.2.2 + 238. http://www.columbia.edu/kermit/ckubwr.html#top + 239. http://www.columbia.edu/kermit/ckubwr.html#contents + 240. http://www.columbia.edu/kermit/ckubwr.html#x3.2.4 + 241. http://www.columbia.edu/kermit/ckubwr.html#x3.2.4.3 + 242. http://www.columbia.edu/kermit/ckubwr.html#x3.2.4.1 + 243. http://www.columbia.edu/kermit/ckubwr.html#top + 244. http://www.columbia.edu/kermit/ckubwr.html#contents + 245. http://www.columbia.edu/kermit/ckubwr.html#x3.2.4 + 246. http://www.columbia.edu/kermit/ckubwr.html#x3.2.4.4 + 247. http://www.columbia.edu/kermit/ckubwr.html#x3.2.4.2 + 248. http://www.columbia.edu/kermit/ckubwr.html#top + 249. http://www.columbia.edu/kermit/ckubwr.html#contents + 250. http://www.columbia.edu/kermit/ckubwr.html#x3.2.4 + 251. http://www.columbia.edu/kermit/ckubwr.html#x3.2.4.5 + 252. http://www.columbia.edu/kermit/ckubwr.html#x3.2.4.3 + 253. http://www.columbia.edu/kermit/ckubwr.html#top + 254. http://www.columbia.edu/kermit/ckubwr.html#contents + 255. http://www.columbia.edu/kermit/ckubwr.html#x3.2.4 + 256. http://www.columbia.edu/kermit/ckubwr.html#x3.2.4.4 + 257. http://www.columbia.edu/kermit/ckubwr.html#top + 258. http://www.columbia.edu/kermit/ckubwr.html#contents + 259. http://www.columbia.edu/kermit/ckubwr.html#x3.2 + 260. http://www.columbia.edu/kermit/ckubwr.html#x3.2.4 + 261. http://www.columbia.edu/kermit/ckubwr.html#top + 262. http://www.columbia.edu/kermit/ckubwr.html#contents + 263. http://www.columbia.edu/kermit/ckubwr.html#x3 + 264. http://www.columbia.edu/kermit/ckubwr.html#x3.4 + 265. http://www.columbia.edu/kermit/ckubwr.html#x3.2 + 266. http://www.columbia.edu/kermit/ckubwr.html#x3.3.1 + 267. http://www.columbia.edu/kermit/ckubwr.html#x3.3.2 + 268. http://www.columbia.edu/kermit/ckubwr.html#x3.3.3 + 269. http://www.columbia.edu/kermit/ckubwr.html#x3.3.4 + 270. http://www.columbia.edu/kermit/ckubwr.html#x3.3.5 + 271. http://www.columbia.edu/kermit/ckubwr.html#x3.3.6 + 272. http://en.wikipedia.org/wiki/Avahi_(software) + 273. news:comp.os.linux.misc + 274. news:comp.os.linux.answers + 275. http://www.tldp.org/ + 276. http://www.tldp.org/FAQ/Linux-FAQ.html + 277. http://www.tldp.org/HOWTO/Serial-HOWTO.html + 278. http://tldp.org/HOWTO/Modem-HOWTO.html + 279. ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO + 280. ftp://tsx-11.mit.edu/pub/linux/docs/HOWTO + 281. http://www.tldp.org/HOWTO/ + 282. http://www.tldp.org/hmirrors.html + 283. http://www.redhat.com/apps/support/ + 284. http://www.debian.org/support + 285. http://www.slackware.com/support/ + 286. http://www.caldera.com/support/ + 287. http://www.novell.com/support/microsites/microsite.do + 288. http://www.mandrake.com/support/ + 289. http://www.turbolinux.com/support/ + 290. http://www.linmodems.org/ + 291. http://www.columbia.edu/kermit/ckubwr.html#x3.0 + 292. http://linux.dreamtime.org/decnet/ + 293. mailto:kermit-support@columbia.edu + 294. http://www.linmodems.org/ + 295. http://www.columbia.edu/kermit/ckubwr.html#x3.0.2 + 296. http://www.columbia.edu/kermit/security.html#servers + 297. http://www.columbia.edu/kermit/sshclient.html + 298. http://www.columbia.edu/kermit/ckubwr.html#top + 299. http://www.columbia.edu/kermit/ckubwr.html#contents + 300. http://www.columbia.edu/kermit/ckubwr.html#x3 + 301. http://www.columbia.edu/kermit/ckubwr.html#x3.3.2 + 302. http://www.columbia.edu/kermit/ckubwr.html#top + 303. http://www.columbia.edu/kermit/ckubwr.html#contents + 304. http://www.columbia.edu/kermit/ckubwr.html#x3.3 + 305. http://www.columbia.edu/kermit/ckubwr.html#x3.3.3 + 306. http://www.columbia.edu/kermit/ckubwr.html#x3.3.1 + 307. http://www.columbia.edu/kermit/ckubwr.html#x3.0 + 308. http://www.columbia.edu/kermit/ckubwr.html#x6 + 309. http://www.columbia.edu/kermit/ckubwr.html#x7 + 310. http://www.columbia.edu/kermit/ckubwr.html#x8 + 311. http://www.columbia.edu/kermit/ckuins.html#x10 + 312. http://www.columbia.edu/kermit/ckuins.html#x11 + 313. http://www.columbia.edu/kermit/ckuins.html + 314. http://www.columbia.edu/kermit/ckubwr.html#x3.0 + 315. http://linuxwww.db.erau.edu/mail_archives/linux-kernel/Mar_98/1441.html + 316. http://www.columbia.edu/kermit/ckubwr.html#top + 317. http://www.columbia.edu/kermit/ckubwr.html#contents + 318. http://www.columbia.edu/kermit/ckubwr.html#x3.3 + 319. http://www.columbia.edu/kermit/ckubwr.html#x3.3.4 + 320. http://www.columbia.edu/kermit/ckubwr.html#x3.3.2 + 321. http://www.columbia.edu/kermit/ckubwr.html#x3.0.5 + 322. http://www.columbia.edu/kermit/ckfaq.html#term + 323. http://dickey.his.com/xterm/xterm.html + 324. http://dickey.his.com/xterm/xterm.html + 325. ftp://kermit.columbia.edu/kermit/f/xmodmap.txt + 326. http://www.columbia.edu/kermit/ckubwr.html#top + 327. http://www.columbia.edu/kermit/ckubwr.html#contents + 328. http://www.columbia.edu/kermit/ckubwr.html#x3.3 + 329. http://www.columbia.edu/kermit/ckubwr.html#x3.3.5 + 330. http://www.columbia.edu/kermit/ckubwr.html#x3.3.3 + 331. http://www.columbia.edu/kermit/ckubwr.html#top + 332. http://www.columbia.edu/kermit/ckubwr.html#contents + 333. http://www.columbia.edu/kermit/ckubwr.html#x3.3 + 334. http://www.columbia.edu/kermit/ckubwr.html#x3.3.6 + 335. http://www.columbia.edu/kermit/ckubwr.html#x3.3.4 + 336. http://www.columbia.edu/kermit/ckermit.html + 337. mailto:kermit-support@columbia.edu + 338. http://www.redhat.com/support/errata/RHBA-2001-153.html + 339. news:comp.protocols.kermit.misc + 340. http://www.columbia.edu/kermit/ckubwr.html#top + 341. http://www.columbia.edu/kermit/ckubwr.html#contents + 342. http://www.columbia.edu/kermit/ckubwr.html#x3.3 + 343. http://www.columbia.edu/kermit/ckubwr.html#x3.3.5 + 344. http://www.columbia.edu/kermit/ckubwr.html#top + 345. http://www.columbia.edu/kermit/ckubwr.html#contents + 346. http://www.columbia.edu/kermit/ckubwr.html#x3 + 347. http://www.columbia.edu/kermit/ckubwr.html#x3.5 + 348. http://www.columbia.edu/kermit/ckubwr.html#x3.3 + 349. http://www.columbia.edu/kermit/ckubwr.html#top + 350. http://www.columbia.edu/kermit/ckubwr.html#contents + 351. http://www.columbia.edu/kermit/ckubwr.html#x3 + 352. http://www.columbia.edu/kermit/ckubwr.html#x3.6 + 353. http://www.columbia.edu/kermit/ckubwr.html#x3.4 + 354. news:comp.os.qnx + 355. http://www.columbia.edu/kermit/gkermit.html + 356. http://www.columbia.edu/kermit/ckuins.html#x10 + 357. http://www.columbia.edu/kermit/ckuins.html + 358. http://www.columbia.edu/kermit/ckubwr.html#top + 359. http://www.columbia.edu/kermit/ckubwr.html#contents + 360. http://www.columbia.edu/kermit/ckubwr.html#x3 + 361. http://www.columbia.edu/kermit/ckubwr.html#x3.7 + 362. http://www.columbia.edu/kermit/ckubwr.html#x3.5 + 363. http://www.columbia.edu/kermit/ckubwr.html#x3.6.1 + 364. http://www.columbia.edu/kermit/ckubwr.html#x3.6.2 + 365. http://www.columbia.edu/kermit/ckubwr.html#x3.6.3 + 366. http://www.columbia.edu/kermit/ckubwr.html#x3.6.4 + 367. http://www.columbia.edu/kermit/ckubwr.html#x3.10 + 368. http://aplawrence.com/SCOFAQ/ + 369. http://www.zenez.com/cgi-bin/scoprogfaq/faq.pl + 370. http://www.zenez.com/cgi-bin/scouw7faq/faq.pl + 371. http://zenez.pcunix.com/cgi-bin/scouw7faq/faq.pl + 372. http://pcunix.com/Unixart/modems.html + 373. http://www.freebird.org/faq/ + 374. http://www.freebird.org/faq/developer.html + 375. http://support.caldera.com/caldera + 376. http://stage.caldera.com/ta/ + 377. http://aplawrence.com/newtosco.html + 378. http://www.columbia.edu/kermit/ckubwr.html#x3.0.5 + 379. http://www.columbia.edu/kermit/ckfaq.html#term + 380. http://www.columbia.edu/kermit/ckubwr.html#x3.0 + 381. http://www.columbia.edu/kermit/ckubwr.html#top + 382. http://www.columbia.edu/kermit/ckubwr.html#contents + 383. http://www.columbia.edu/kermit/ckubwr.html#x3.6 + 384. http://www.columbia.edu/kermit/ckubwr.html#x3.6.1 + 385. ftp://kermit.columbia.edu/kermit/c-kermit/ckutio.c + 386. http://www.columbia.edu/kermit/ckubwr.html#top + 387. http://www.columbia.edu/kermit/ckubwr.html#contents + 388. http://www.columbia.edu/kermit/ckubwr.html#x3.6 + 389. http://www.columbia.edu/kermit/ckubwr.html#x3.6.3 + 390. http://www.columbia.edu/kermit/ckubwr.html#x3.6.1 + 391. http://www.digi.com/ + 392. ftp://ftp.fu-berlin.de/pub/unix/driver/fas + 393. http://www.columbia.edu/kermit/ckubwr.html#x14 + 394. http://www.sco.com/ + 395. ftp://ftp.sco.com/ + 396. http://www.columbia.edu/kermit/ckubwr.html#top + 397. http://www.columbia.edu/kermit/ckubwr.html#contents + 398. http://www.columbia.edu/kermit/ckubwr.html#x3.6 + 399. http://www.columbia.edu/kermit/ckubwr.html#x3.6.4 + 400. http://www.columbia.edu/kermit/ckubwr.html#x3.6.2 + 401. http://www.columbia.edu/kermit/ckubwr.html#x3.10 + 402. http://www.columbia.edu/kermit/ckubwr.html#top + 403. http://www.columbia.edu/kermit/ckubwr.html#contents + 404. http://www.columbia.edu/kermit/ckubwr.html#x3.6 + 405. http://www.columbia.edu/kermit/ckubwr.html#x3.6.3 + 406. http://www.columbia.edu/kermit/ckubwr.html#top + 407. http://www.columbia.edu/kermit/ckubwr.html#contents + 408. http://www.columbia.edu/kermit/ckubwr.html#x3 + 409. http://www.columbia.edu/kermit/ckubwr.html#x3.8 + 410. http://www.columbia.edu/kermit/ckubwr.html#x3.6 + 411. http://www.columbia.edu/kermit/ckubwr.html#x3.7.1 + 412. http://www.columbia.edu/kermit/ckubwr.html#x3.7.2 + 413. http://www.columbia.edu/kermit/ckubwr.html#x3.7.3 + 414. http://www.columbia.edu/kermit/ckubwr.html#x3.7.4 + 415. http://www.columbia.edu/kermit/ckubwr.html#x3.7.5 + 416. news:comp.unix.solaris + 417. http://access1.sun.com/ + 418. http://docs.sun.com/ + 419. http://www.sunhelp.com/ + 420. http://www.wins.uva.nl/pub/solaris/solaris2/ + 421. http://www.wins.uva.nl/cgi-bin/sfaq.cgi + 422. ftp://ftp.wins.uva.nl/pub/solaris + 423. http://www.science.uva.nl/pub/solaris/solaris2.html + 424. http://www.stokely.com/ + 425. http://www.stokely.com/unix.sysadm.resources/faqs.sun.html + 426. http://www.columbia.edu/kermit/ckubwr.html#x3.0 + 427. http://www.columbia.edu/kermit/ckubwr.html#top + 428. http://www.columbia.edu/kermit/ckubwr.html#contents + 429. http://www.columbia.edu/kermit/ckubwr.html#x3 + 430. http://www.columbia.edu/kermit/ckubwr.html#x3.7 + 431. http://www.columbia.edu/kermit/ckubwr.html#x3.7.2 + 432. http://www.columbia.edu/kermit/ckubwr.html#top + 433. http://www.columbia.edu/kermit/ckubwr.html#contents + 434. http://www.columbia.edu/kermit/ckubwr.html#x3.7 + 435. http://www.columbia.edu/kermit/ckubwr.html#x3.7.3 + 436. http://www.columbia.edu/kermit/ckubwr.html#x3.7.1 + 437. http://www.columbia.edu/kermit/ckubwr.html#top + 438. http://www.columbia.edu/kermit/ckubwr.html#contents + 439. http://www.columbia.edu/kermit/ckubwr.html#x3.7 + 440. http://www.columbia.edu/kermit/ckubwr.html#x3.7.4 + 441. http://www.columbia.edu/kermit/ckubwr.html#x3.7.2 + 442. http://www.columbia.edu/kermit/ckubwr.html#top + 443. http://www.columbia.edu/kermit/ckubwr.html#contents + 444. http://www.columbia.edu/kermit/ckubwr.html#x3.7 + 445. http://www.columbia.edu/kermit/ckubwr.html#x3.7.5 + 446. http://www.columbia.edu/kermit/ckubwr.html#x3.7.3 + 447. news:comp.os.vms + 448. http://www.columbia.edu/kermit/ckubwr.html#top + 449. http://www.columbia.edu/kermit/ckubwr.html#contents + 450. http://www.columbia.edu/kermit/ckubwr.html#x3.7 + 451. http://www.columbia.edu/kermit/ckubwr.html#x3.7.6 + 452. http://www.columbia.edu/kermit/ckubwr.html#x3.7.4 + 453. http://www.columbia.edu/kermit/ckubwr.html#top + 454. http://www.columbia.edu/kermit/ckubwr.html#contents + 455. http://www.columbia.edu/kermit/ckubwr.html#x3.7 + 456. http://www.columbia.edu/kermit/ckubwr.html#x3.7.5 + 457. http://www.columbia.edu/kermit/ckubwr.html#top + 458. http://www.columbia.edu/kermit/ckubwr.html#contents + 459. http://www.columbia.edu/kermit/ckubwr.html#x3 + 460. http://www.columbia.edu/kermit/ckubwr.html#x3.9 + 461. http://www.columbia.edu/kermit/ckubwr.html#x3.7 + 462. http://www.stokely.com/ + 463. http://access1.sun.com/ + 464. http://www.ludd.luth.se/~bear/project/sun/sun.hardware.txt + 465. ftp://ftp.netcom.com/pub/ru/rubicon/sun.hdwr.ref + 466. ftp://ftp.intnet.net/pub/SUN/Sun-Hardware-Ref + 467. http://www.columbia.edu/kermit/ckubwr.html#top + 468. http://www.columbia.edu/kermit/ckubwr.html#contents + 469. http://www.columbia.edu/kermit/ckubwr.html#x3 + 470. http://www.columbia.edu/kermit/ckubwr.html#x3.10 + 471. http://www.columbia.edu/kermit/ckubwr.html#x3.8 + 472. news:comp.unix.ultrix + 473. news:comp.sys.dec + 474. http://www.columbia.edu/kermit/ckubwr.html#top + 475. http://www.columbia.edu/kermit/ckubwr.html#contents + 476. http://www.columbia.edu/kermit/ckubwr.html#x3 + 477. http://www.columbia.edu/kermit/ckubwr.html#x3.11 + 478. http://www.columbia.edu/kermit/ckubwr.html#x3.9 + 479. http://www.freebird.org/ + 480. http://www.freebird.org/faq/ + 481. news:comp.unix.unixware.misc + 482. news:comp.unix.sco.misc + 483. http://www.columbia.edu/kermit/ckubwr.html#x3.0 + 484. ftp://kermit.columbia.edu/kermit/f/ckutio.c + 485. http://www.columbia.edu/kermit/ckubwr.html#top + 486. http://www.columbia.edu/kermit/ckubwr.html#contents + 487. http://www.columbia.edu/kermit/ckubwr.html#x3 + 488. http://www.columbia.edu/kermit/ckubwr.html#x3.12 + 489. http://www.columbia.edu/kermit/ckubwr.html#x3.10 + 490. http://www.columbia.edu/kermit/ckubwr.html#top + 491. http://www.columbia.edu/kermit/ckubwr.html#contents + 492. http://www.columbia.edu/kermit/ckubwr.html#x3 + 493. http://www.columbia.edu/kermit/ckubwr.html#x3.13 + 494. http://www.columbia.edu/kermit/ckubwr.html#x3.11 + 495. http://www.columbia.edu/kermit/ckubwr.html#top + 496. http://www.columbia.edu/kermit/ckubwr.html#contents + 497. http://www.columbia.edu/kermit/ckubwr.html#x3 + 498. http://www.columbia.edu/kermit/ckubwr.html#x3.14 + 499. http://www.columbia.edu/kermit/ckubwr.html#x3.12 + 500. http://www.columbia.edu/kermit/ckubwr.html#top + 501. http://www.columbia.edu/kermit/ckubwr.html#contents + 502. http://www.columbia.edu/kermit/ckubwr.html#x3 + 503. http://www.columbia.edu/kermit/ckubwr.html#x3.15 + 504. http://www.columbia.edu/kermit/ckubwr.html#x3.13 + 505. news:comp.sys.sgi.misc + 506. news:comp.sys.sgi.admin + 507. http://www.sgi.com/ + 508. http://www-viz.tamu.edu/~sgi-faq/ + 509. ftp://viz.tamu.edu/pub/sgi/faq/ + 510. http://www.columbia.edu/kermit/ckuins.html + 511. http://freeware.sgi.com/Installable/gcc-2.95.2.html + 512. http://freeware.sgi.com/Installable/gcc-2.95.2.html + 513. http://www.columbia.edu/kermit/ckubwr.html#top + 514. http://www.columbia.edu/kermit/ckubwr.html#contents + 515. http://www.columbia.edu/kermit/ckubwr.html#x3 + 516. http://www.columbia.edu/kermit/ckubwr.html#x3.16 + 517. http://www.columbia.edu/kermit/ckubwr.html#x3.14 + 518. news:comp.sys.be + 519. http://www.columbia.edu/kermit/ckubwr.html#top + 520. http://www.columbia.edu/kermit/ckubwr.html#contents + 521. http://www.columbia.edu/kermit/ckubwr.html#x3 + 522. http://www.columbia.edu/kermit/ckubwr.html#x3.17 + 523. http://www.columbia.edu/kermit/ckubwr.html#x3.15 + 524. http://www.columbia.edu/kermit/ckubwr.html#top + 525. http://www.columbia.edu/kermit/ckubwr.html#contents + 526. http://www.columbia.edu/kermit/ckubwr.html#x3 + 527. http://www.columbia.edu/kermit/ckubwr.html#x3.18 + 528. http://www.columbia.edu/kermit/ckubwr.html#x3.16 + 529. http://www.columbia.edu/kermit/ckubwr.html#top + 530. http://www.columbia.edu/kermit/ckubwr.html#contents + 531. http://www.columbia.edu/kermit/ckubwr.html#x3 + 532. http://www.columbia.edu/kermit/ckubwr.html#x3.19 + 533. http://www.columbia.edu/kermit/ckubwr.html#x3.17 + 534. http://www.columbia.edu/kermit/ckubwr.html#top + 535. http://www.columbia.edu/kermit/ckubwr.html#contents + 536. http://www.columbia.edu/kermit/ckubwr.html#x3 + 537. http://www.columbia.edu/kermit/ckubwr.html#x3.20 + 538. http://www.columbia.edu/kermit/ckubwr.html#x3.18 + 539. http://www.columbia.edu/kermit/mac.html + 540. http://www.amazon.com/gp/product/B0000VYJRY?ie=UTF8&tag=aleidmoreldom-20&linkCode=as2&camp=1789&creative=390957&creativeASIN=B0000VYJRY + 541. http://www.columbia.edu/kermit/ckuins.html#x10 + 542. http://www.columbia.edu/kermit/ckuins.html + 543. http://www.amazon.com/gp/product/B000FX61MS?ie=UTF8&tag=aleidmoreldom-20&linkCode=as2&camp=1789&creative=390957&creativeASIN=B000FX61MS + 544. mailto:kermit@columbia.edu + 545. http://www.columbia.edu/kermit/ckubwr.html#top + 546. http://www.columbia.edu/kermit/ckubwr.html#contents + 547. http://www.columbia.edu/kermit/ckubwr.html#x3 + 548. http://www.columbia.edu/kermit/ckubwr.html#x3.19 + 549. http://www.uni-giessen.de/faq/archiv/coherent-faq.general/msg00000.html + 550. http://www.columbia.edu/kermit/ckubwr.html#top + 551. http://www.columbia.edu/kermit/ckubwr.html#contents + 552. http://www.columbia.edu/kermit/ckubwr.html#x5 + 553. http://www.columbia.edu/kermit/ckubwr.html#x3 + 554. http://www.columbia.edu/kermit/ckccfg.html + 555. http://www.columbia.edu/kermit/ckubwr.html#top + 556. http://www.columbia.edu/kermit/ckubwr.html#contents + 557. http://www.columbia.edu/kermit/ckubwr.html#x6 + 558. http://www.columbia.edu/kermit/ckubwr.html#x4 + 559. http://www.columbia.edu/kermit/ckuins.html + 560. http://www.columbia.edu/kermit/ckubwr.html#top + 561. http://www.columbia.edu/kermit/ckubwr.html#contents + 562. http://www.columbia.edu/kermit/ckubwr.html#x7 + 563. http://www.columbia.edu/kermit/ckubwr.html#x5 + 564. http://www.columbia.edu/kermit/ckuins.html#9.5 + 565. http://www.columbia.edu/kermit/ckubwr.html#x3 + 566. http://www.columbia.edu/kermit/ckubwr.html#top + 567. http://www.columbia.edu/kermit/ckubwr.html#contents + 568. http://www.columbia.edu/kermit/ckubwr.html#x8 + 569. http://www.columbia.edu/kermit/ckubwr.html#x6 + 570. http://www.columbia.edu/kermit/ckuins.html#x8 + 571. http://www.columbia.edu/kermit/ckuins.html + 572. http://www.columbia.edu/kermit/ck60manual.html + 573. http://www.columbia.edu/kermit/cable.html + 574. http://www.columbia.edu/kermit/ckubwr.html#top + 575. http://www.columbia.edu/kermit/ckubwr.html#contents + 576. http://www.columbia.edu/kermit/ckubwr.html#x9 + 577. http://www.columbia.edu/kermit/ckubwr.html#x7 + 578. http://www.columbia.edu/kermit/ckubwr.html#top + 579. http://www.columbia.edu/kermit/ckubwr.html#contents + 580. http://www.columbia.edu/kermit/ckubwr.html#x10 + 581. http://www.columbia.edu/kermit/ckubwr.html#x8 + 582. http://www.columbia.edu/kermit/ck60manual.html + 583. http://dickey.his.com/xterm/xterm.html + 584. http://www.columbia.edu/kermit/ckubwr.html#top + 585. http://www.columbia.edu/kermit/ckubwr.html#contents + 586. http://www.columbia.edu/kermit/ckubwr.html#x11 + 587. http://www.columbia.edu/kermit/ckubwr.html#x9 + 588. http://www.columbia.edu/kermit/ckubwr.html#top + 589. http://www.columbia.edu/kermit/ckubwr.html#contents + 590. http://www.columbia.edu/kermit/ckubwr.html#x12 + 591. http://www.columbia.edu/kermit/ckubwr.html#x10 + 592. http://www.columbia.edu/kermit/ckubwr.html#x11.1 + 593. http://www.columbia.edu/kermit/ckubwr.html#x11.2 + 594. http://www.columbia.edu/kermit/ckubwr.html#top + 595. http://www.columbia.edu/kermit/ckubwr.html#contents + 596. http://www.columbia.edu/kermit/ckubwr.html#x11 + 597. http://www.columbia.edu/kermit/ckubwr.html#x11.2 + 598. http://www.columbia.edu/kermit/ck60manual.html + 599. http://www.columbia.edu/kermit/ckubwr.html#top + 600. http://www.columbia.edu/kermit/ckubwr.html#contents + 601. http://www.columbia.edu/kermit/ckubwr.html#x11 + 602. http://www.columbia.edu/kermit/ckubwr.html#x11.1 + 603. http://www.columbia.edu/kermit/ck60manual.html + 604. http://www.columbia.edu/kermit/ckubwr.html#top + 605. http://www.columbia.edu/kermit/ckubwr.html#contents + 606. http://www.columbia.edu/kermit/ckubwr.html#x13 + 607. http://www.columbia.edu/kermit/ckubwr.html#x11 + 608. http://www.columbia.edu/kermit/security.html + 609. http://www.columbia.edu/kermit/ckubwr.html#top + 610. http://www.columbia.edu/kermit/ckubwr.html#contents + 611. http://www.columbia.edu/kermit/ckubwr.html#x14 + 612. http://www.columbia.edu/kermit/ckubwr.html#x12 + 613. http://www.columbia.edu/kermit/ckubwr.html#top + 614. http://www.columbia.edu/kermit/ckubwr.html#contents + 615. http://www.columbia.edu/kermit/ckubwr.html#x15 + 616. http://www.columbia.edu/kermit/ckubwr.html#x14 + 617. mailto:support@stallion.oz.au + 618. http://www.stallion.com/ + 619. http://www.columbia.edu/kermit/ckubwr.html#top + 620. http://www.columbia.edu/kermit/ckubwr.html#contents + 621. http://www.columbia.edu/kermit/ckermit.html + 622. http://www.columbia.edu/kermit/ck80.html + 623. http://www.columbia.edu/kermit/index.html + 624. http://www.columbia.edu/kermit/index.html + 625. http://www.columbia.edu/ + 626. mailto:kermit@columbia.edu diff --git a/ckucmd.c b/ckucmd.c index 3ea4807..274dc2d 100644 --- a/ckucmd.c +++ b/ckucmd.c @@ -190,7 +190,13 @@ modules would have to be changed... #endif /* CK_ANSIC */ #endif /* OSF13 */ +#ifndef HPUXPRE65 #include /* Error number symbols */ +#else +#ifndef ERRNO_INCLUDED +#include /* Error number symbols */ +#endif /* ERRNO_INCLUDED */ +#endif /* HPUXPRE65 */ #ifdef OS2 #ifndef NT diff --git a/ckucon.c b/ckucon.c index 776682d..50ceb7e 100644 --- a/ckucon.c +++ b/ckucon.c @@ -1,13 +1,13 @@ #include "ckcsym.h" -char *connv = "CONNECT Command for UNIX:fork(), 9.0.116, 1 Mar 2010"; +char *connv = "CONNECT Command for UNIX:fork(), 9.0.117, 14 Jul 2011"; /* C K U C O N -- Terminal connection to remote system, for UNIX */ /* Author: Frank da Cruz , Columbia University Academic Information Systems, New York City. - Copyright (C) 1985, 2010, + Copyright (C) 1985, 2011, Trustees of Columbia University in the City of New York. All rights reserved. See the C-Kermit COPYING.TXT file or the copyright text in the ckcmai.c module for disclaimer and permissions. @@ -43,7 +43,14 @@ _PROTOTYP( static VOID concld, (void) ); #endif /* NEXT */ #include /* Signals */ -#include /* Error numbers */ + +#ifndef HPUXPRE65 +#include /* Error number symbols */ +#else +#ifndef ERRNO_INCLUDED +#include /* Error number symbols */ +#endif /* ERRNO_INCLUDED */ +#endif /* HPUXPRE65 */ #ifdef ZILOG /* Longjumps */ #include diff --git a/ckufio.c b/ckufio.c index d860757..b5bfaae 100644 --- a/ckufio.c +++ b/ckufio.c @@ -3,12 +3,12 @@ #define CK_NONBLOCK /* See zoutdump() */ #ifdef aegis -char *ckzv = "Aegis File support, 9.0.215, 13 Jun 2011"; +char *ckzv = "Aegis File support, 9.0.216, 20 Aug 2011"; #else #ifdef Plan9 -char *ckzv = "Plan 9 File support, 9.0.215, 13 Jun 2011"; +char *ckzv = "Plan 9 File support, 9.0.216, 20 Aug 2011"; #else -char *ckzv = "UNIX File support, 9.0.215, 13 Jun 2011"; +char *ckzv = "UNIX File support, 9.0.216, 20 Aug 2011"; #endif /* Plan9 */ #endif /* aegis */ /* @@ -69,7 +69,14 @@ _PROTOTYP( int parser, ( int ) ); #endif /* OSF13 */ #endif /* COMMENT */ -#include +#ifndef HPUXPRE65 +#include /* Error number symbols */ +#else +#ifndef ERRNO_INCLUDED +#include /* Error number symbols */ +#endif /* ERRNO_INCLUDED */ +#endif /* HPUXPRE65 */ + #include #ifdef MINIX2 @@ -1062,6 +1069,7 @@ logwtmp __P ((__const char *__ut_line, __const char *__ut_name, #endif /* IRIX60 */ #endif /* SOLARIS */ #endif /* HAVEUTMPX */ + #ifdef HAVEUTMPX #include #else @@ -1150,7 +1158,11 @@ logwtmp(line, name, host) char *line, *name, *host; } if (!fstat(wtmpfd, &buf)) { ckstrncpy(ut.ut_line, line, sizeof(ut.ut_line)); +#ifdef FREEBSD9 + ckstrncpy(ut.ut_user, name, sizeof(ut.ut_user)); +#else ckstrncpy(ut.ut_name, name, sizeof(ut.ut_name)); +#endif /* FREEBSD9 */ #ifdef HAVEUTHOST /* Not portable */ ckstrncpy(ut.ut_host, host, sizeof(ut.ut_host)); diff --git a/ckuins.txt b/ckuins.txt index 6176dad..08cfedb 100644 --- a/ckuins.txt +++ b/ckuins.txt @@ -13,8 +13,8 @@ C-Kermit 9.0 Installation Instructions and Options for Unix The Kermit Project Columbia University - As of C-Kermit version: 9.0.300, 30 June 2011 - This file last updated: Tue Jun 28 08:28:08 2011 (New York City + As of C-Kermit version: 9.0.302, 20 August 2011 + This file last updated: Sun Aug 21 12:08:29 2011 (New York City time) IF YOU ARE READING A PLAIN-TEXT version of this document, it is a @@ -157,12 +157,12 @@ OVERVIEW Thus, a well-crafted installation procedure should present the options and allow the installer to choose the method, if any, for regulating - accesss to the dialout devices: + access to the dialout devices: a. Check the permissions of the lockfile directory and the dialout - devices. If they do not allow group or world R/W accesss, then: + devices. If they do not allow group or world R/W access, then: b. "Your UUCP lockfile directory and/or dialout devices require - privilege to accesss. You must either change their permissions or + privilege to access. You must either change their permissions or install Kermit with privileges." c. "If you wish to install Kermit with privileges, it will be given the same owner, group, and permissions as the cu program so it can @@ -196,7 +196,7 @@ OVERVIEW Hundreds of prebuilt C-Kermit binaries are available on the CDROM in the BINARY tree [NOTE: The C-Kermit CDROM is still for version 7.0], and at our ftp site in the [72]kermit/bin area (with names starting - with "ck"), also accesssible on the [73]C-Kermit website. To install a + with "ck"), also accessible on the [73]C-Kermit website. To install a prebuilt binary: a. Rename the binary to "wermit". @@ -355,7 +355,7 @@ ln -s kermit telnet (Also see the [110]Configurations Options document, [111]Section 8). Lots of new features have been added in versions 7.0 and 8.0 that - require accesss to new symbols, APIs, libraries, etc, and this will no + require access to new symbols, APIs, libraries, etc, and this will no doubt cause problems in compiling, linking, or execution on platforms where 6.0 and earlier built without incident. This section contains what we know as of the date of this file. @@ -1172,6 +1172,10 @@ touch ckcpro.c make particular connections, execute complicated scripts, whatever you want. + And in C-Kermit 9.0 the initialization has indeed been "retired" by + renaming it to okermit.ini, and replaced by a stub ckermit.ini that + doesn't do anything but print a message. Ditto for ckermod.ini. + 5.2. Text Files These are entirely optional. Many of them are to be found at the Kermit @@ -1202,38 +1206,43 @@ touch ckcpro.c the Kermit website as: [183]http://www.columbia.edu/kermit/ckermit80.html - [184]ckcbwr.txt + [184]ckermit90.txt + Supplement to [185]Using C-Kermit for version 9.0. Available on + the Kermit website as: + [186]http://www.columbia.edu/kermit/ckermit90.html + + [187]ckcbwr.txt The general C-Kermit hints and tips ("beware") file. Available on the Kermit website as: - [185]http://www.columbia.edu/kermit/ckcbwr.html + [188]http://www.columbia.edu/kermit/ckcbwr.html - [186]ckubwr.txt + [189]ckubwr.txt The Unix-specific C-Kermit hints and tips file. Available on the Kermit website as: - [187]http://www.columbia.edu/kermit/ckubwr.html + [190]http://www.columbia.edu/kermit/ckubwr.html - [188]ckuins.txt + [191]ckuins.txt Unix C-Kermit Installation Instructions (this file). Available on the Kermit website as: - [189]http://www.columbia.edu/kermit/ckuins.html + [192]http://www.columbia.edu/kermit/ckuins.html - [190]ckccfg.txt + [193]ckccfg.txt C-Kermit compile-time configuration options. Available on the Kermit website as: - [191]http://www.columbia.edu/kermit/ckccfg.html + [194]http://www.columbia.edu/kermit/ckccfg.html - [192]ckcplm.txt + [195]ckcplm.txt The C-Kermit program logic manual. Available on the Kermit website as: - [193]http://www.columbia.edu/kermit/ckcplm.html + [196]http://www.columbia.edu/kermit/ckcplm.html - [194]ca_certs.pem + [197]ca_certs.pem Certificate Authority certificates for secure connections (see - [195]Section 16). + [198]Section 16). 5.3. Installing the Kermit Files - There is an "install" target in the [196]makefile that you can use if + There is an "install" target in the [199]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. @@ -1247,7 +1256,7 @@ touch ckcpro.c available. In most cases, you need to be root to install C-Kermit, if only to gain - write accesss to directories in which the binary and manual page are to + 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 @@ -1264,11 +1273,11 @@ chmod 755 /usr/local/bin/kermit make install IMPORTANT: IF C-KERMIT IS TO BE USED FOR DIALING OUT, you must also do - something to give it accesss to the dialout devices and lockfile + 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 - [197]Sections 10 and [198]11 below, make the necessary decisions, and + [200]Sections 10 and [201]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 @@ -1276,7 +1285,7 @@ make install appropriately, e.g. to kermit.1. This is also taken care of by "make install". - Optionally, the text files listed in the [199]previous section can be + Optionally, the text files listed in the [202]previous section can be placed in a publicly readable directory. Suggested directory names are: /usr/local/doc/kermit/ @@ -1306,10 +1315,10 @@ K_INFO_DIR give it the information it needs by setting the variables described below. You can use this target if: - * You downloaded the [200]complete C-Kermit archive and built + * You downloaded the [203]complete C-Kermit archive and built C-Kermit from source; or: - * You downloaded an [201]individual C-Kermit binary and the - [202]C-Kermit text-file archive, and your computer has a "make" + * You downloaded an [204]individual C-Kermit binary and the + [205]C-Kermit text-file archive, and your computer has a "make" command. Here are the parameters you need to know: @@ -1430,7 +1439,7 @@ CERTDIR = 6. INSTALLING UNIX C-KERMIT FROM DOS-FORMAT DISKETTES - [ [203]Top ] [ [204]Contents ] [ [205]Next ] [ [206]Previous ] + [ [206]Top ] [ [207]Contents ] [ [208]Next ] [ [209]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. @@ -1490,7 +1499,7 @@ done 7. CHECKING THE RESULTS - [ [207]Top ] [ [208]Contents ] [ [209]Next ] [ [210]Previous ] + [ [210]Top ] [ [211]Contents ] [ [212]Next ] [ [213]Previous ] First some quick checks for problems that can be easily corrected by recompiling with different options: @@ -1531,14 +1540,14 @@ done a. Start C-Kermit (usually by typing "./wermit" in the directory where you ran the makefile). Do you see the C-Kermit> prompt? If not, C-Kermit incorrectly deduced that it was running in the background. - The test is in conbgt() in [211]ckutio.c. If you can fix it for + The test is in conbgt() in [214]ckutio.c. If you can fix it for your system, please send in the fix (Hint: read about "PID_T" below). Otherwise, you can force C-Kermit to foreground mode by starting it with the -z command line option, as in "kermit -z", or giving the interactive command SET BACKGROUND OFF. b. When you type characters at the C-Kermit prompt, do they echo immediately? If not, something is wrong with concb() and probably - the other terminal mode settings routines in [212]ckutio.c. Be sure + the other terminal mode settings routines in [215]ckutio.c. Be sure you have used the most appropriate make entry. c. At the C-Kermit> prompt, type "send ./?". C-Kermit should list all the files in the current directory. If not, it was built for the @@ -1547,7 +1556,7 @@ done d. CD to a directory that contains a variety of files, symlinks, and subdirectories and give a DIRECTORY command at the C-Kermit> prompt. Do the permissions, size, and date appear correct? If not - see [213]Section 4.0. + see [216]Section 4.0. e. Assuming your platform supports long file names, create a file with a long name in your current directory, e.g.: @@ -1562,22 +1571,22 @@ $ touch thisisafilewithaveryveryveryveryveryveryveryverylooooooooongname f. Make sure that Kermit has the maximum path length right. Just type SHOW FILE and see what it says about this. If it is too short, there could be some problems at runtime. To correct, look in - [214]ckcdeb.h to see how the symbol CKMAXPATH is set and make any + [217]ckcdeb.h to see how the symbol CKMAXPATH is set and make any needed adjustments. g. Send a file to your new Kermit program from a different Kermit program that is known to work. Is the date/timestamp of the new file identical to the original? If not, adjustments are needed in - zstrdt() in [215]ckufio.c. + zstrdt() in [218]ckufio.c. h. Go to another computer (Computer B) from which you can send files to C-Kermit. Connect Computer B to the computer (A) where you are testing C-Kermit. Then: i. Send a file from B to A. Make sure it transferred OK and was - created with the the right name. + created with the right name. j. Send a file from B to A, specifying an "as-name" that is very, very long (longer than the maximum name length on computer A). Check to make sure that the file was received OK and that its name was truncated to Computer A's maximum length. If not, check the - MAXNAMLEN definition in [216]ckufio.c. + MAXNAMLEN definition in [219]ckufio.c. k. Tell C-Kermit on Computer A to "set receive pathnames relative" and then send it a file from Computer B specifying an as-name that contains several directory segments: @@ -1606,16 +1615,16 @@ send foo dir1/dir2/dir3/foo became totally frozen, then you are probably running C-Kermit on a Unix version that supports job control, but under a shell that doesn't. If that's not the case, look in the congm() and psuspend() - routines in [217]ckutio.c and see if you can figure out what's + routines in [220]ckutio.c and see if you can figure out what's wrong. If you can't, rebuild with -DNOJC. o. Give a SET LINE command for a dialout device, e.g. "set line - /dev/tty00". If you got some kind of permission or accesss denied - message, go read [218]Section 10 and then come back here. + /dev/tty00". If you got some kind of permission or access denied + message, go read [221]Section 10 and then come back here. p. After giving a successful SET LINE command, type "show comm" to see the communication parameters. Do they make sense? q. Type "set speed ?" and observe the list of available speeds. Is it - what you expected? If not, see [219]Section 2) of the - [220]Configurations Options document. + what you expected? If not, see [222]Section 2) of the + [223]Configurations Options document. r. Give a SET SPEED command to change the device's speed. Did it work? (Type "show comm" again to check.) s. Try dialing out: SET MODEM TYPE , SET LINE , SET SPEED , DIAL . If @@ -1632,16 +1641,16 @@ send foo dir1/dir2/dir3/foo w. If your version was built with fullscreen file transfer display support, check that it works during local-mode file transfer. Also, check C-Kermit's operation afterwards: is the echoing funny? etc - etc. If there are problems, see [221]Section 4. + etc. If there are problems, see [224]Section 4. x. If your version was built with script programming language support, TAKE the ckedemo.ksc file to give it a workout. y. Does C-Kermit interlock correctly with UUCP-family programs (cu, - tip, uucp, etc)? If not, read the section [222]DIALING OUT AND + tip, uucp, etc)? If not, read the section [225]DIALING OUT AND COORDINATING WITH UUCP below. z. Modem signals... Give a SET LINE command to a serial device and then type the SHOW MODEM command. If it says "Modem signals unavailable in this version of Kermit", then you might want to look - at the ttgmdm() routine in [223]ckutio.c and add the needed code -- + at the ttgmdm() routine in [226]ckutio.c and add the needed code -- if indeed your version of Unix provides a way to get modem signals (some don't; e.g. modem signals are a foreign concept to POSIX, requiring politically incorrect workarounds). @@ -1652,7 +1661,7 @@ send foo dir1/dir2/dir3/foo To test, SET LINE , SET MODEM NONE, and HANGUP. The DTR light should go out momentarily. If it doesn't, see if you can add the needed code for your system to the tthang() routine in - [224]ckutio.c. + [227]ckutio.c. ac. If your version of Kermit has the SET FLOW RTS/CTS command, check to see if it works: give Kermit this command, set your modem for RTS/CTS, transfer some files (using big packet and window sizes) @@ -1660,29 +1669,29 @@ send foo dir1/dir2/dir3/foo off (and Kermit does not get packet errors), then it works. If your version of Kermit does not have this command, but your version of Unix does support hardware flow control, take a look at the - tthflow() command in [225]ckutio.c and see if you can add the - needed code (see the section on [226]HARDWARE FLOW CONTROL below). - (And please [227]send back any added code, so that others can + tthflow() command in [228]ckutio.c and see if you can add the + needed code (see the section on [229]HARDWARE FLOW CONTROL below). + (And please [230]send back any added code, so that others can benefit from it and it can be carried forward into future releases.) ad. If C-Kermit starts normally and issues its prompt, echoing is normal, etc, but then after returning from a CONNECT session, the prompt no longer appears, try rebuilding with -DCKCONINTB4CB. ae. (8.0.206 or later) Type some commands at the C-Kermit prompt. Can - you use the Up-arrow and Down-arrow keys on your keyboard to - accesss Kermit's command history? If not, and you're a programmer, - take a look at the USE_ARROWKEYS sections of ckucmd.c. + you use the Up-arrow and Down-arrow keys on your keyboard to access + Kermit's command history? If not, and you're a programmer, take a + look at the USE_ARROWKEYS sections of ckucmd.c. 8. REDUCING THE SIZE OF THE EXECUTABLE PROGRAM IMAGE - [ [228]Top ] [ [229]Contents ] [ [230]Next ] [ [231]Previous ] + [ [231]Top ] [ [232]Contents ] [ [233]Next ] [ [234]Previous ] - Also see: [232]C-Kermit Configuration Options + Also see: [235]C-Kermit Configuration Options a. Many of C-Kermit's options and features can be deselected at compile time. The greatest savings at the least sacrifice in functionality is to disable the logging of debug information by - defining NODEBUG during compilation. See the [233]Configurations + defining NODEBUG during compilation. See the [236]Configurations Options document for further information. b. Use shared libraries rather than static linking. This is the default on many Unix systems anyway. However, executables built for @@ -1702,22 +1711,22 @@ send foo dir1/dir2/dir3/foo 9. UNIX VERSIONS - [ [234]Top ] [ [235]Contents ] [ [236]Next ] [ [237]Previous ] + [ [237]Top ] [ [238]Contents ] [ [239]Next ] [ [240]Previous ] SECTION CONTENTS -9.1 [238]Standards - 9.1.1. [239]POSIX - 9.1.2. [240]ANSI C - 9.1.3. [241]Other Standards -9.2. [242]Library Issues -9.3. [243]Unix File System Peculiarities -9.4. [244]Hardware Flow Control -9.5. [245]Terminal Speeds -9.6. [246]Millisecond Sleeps -9.7. [247]Nondestructive Input Buffer Peeking -9.8. [248]Other System-Dependent Features -9.9. [249]Terminal Interruption +9.1 [241]Standards + 9.1.1. [242]POSIX + 9.1.2. [243]ANSI C + 9.1.3. [244]Other Standards +9.2. [245]Library Issues +9.3. [246]Unix File System Peculiarities +9.4. [247]Hardware Flow Control +9.5. [248]Terminal Speeds +9.6. [249]Millisecond Sleeps +9.7. [250]Nondestructive Input Buffer Peeking +9.8. [251]Other System-Dependent Features +9.9. [252]Terminal Interruption There are several major varieties of Unix: Bell Laboratories Seventh Edition, AT&T System V, Berkeley Standard Distribution (BSD), and @@ -1772,7 +1781,7 @@ send foo dir1/dir2/dir3/foo APIs to get at serial speeds higher than 38400, but then doing so removes hardware flow control -- just when we need it most! In cases like this, dirty tricks are the only recourse (search for SCO_OSR504 in - [250]ckutio.c for examples). + [253]ckutio.c for examples). For reasons like this, Unix implementations tend to be neither pure AT&T nor pure BSD nor pure POSIX, but a mixture of two or more of @@ -1789,13 +1798,13 @@ send foo dir1/dir2/dir3/foo 9.1. Standards - [ [251]Top ] [ [252]Section Contents ] [ [253]Contents ] [ [254]Next ] + [ [254]Top ] [ [255]Section Contents ] [ [256]Contents ] [ [257]Next ] SUBSECTION CONTENTS -9.1.1. [255]POSIX -9.1.2. [256]ANSI C -9.1.3. [257]Other Standards +9.1.1. [258]POSIX +9.1.2. [259]ANSI C +9.1.3. [260]Other Standards In edits 166-167 (1988-89), C-Kermit was heavily modified to try to keep abreast of new standards while still remaining compatible with old @@ -1833,7 +1842,7 @@ send foo dir1/dir2/dir3/foo have some degree of POSIX compliance, but still use BSD or AT&T specific features. - The dilimma is this: it is often necessary to define _POSIX_SOURCE to + The dilemma is this: it is often necessary to define _POSIX_SOURCE to get at new or modern features, such as high serial speeds and the APIs to deal with them. But defining _POSIX_SOURCE also hides other APIs that Kermit needs, for example the ones dealing with modem signals @@ -1918,8 +1927,8 @@ make posix "KFLAGS=-DHDBUUCP" 9.1.2. ANSI C - [ [258]Top ] [ [259]Contents ] [ [260]Section Contents ] [ - [261]Subsection Contents ] [ [262]Next ] [ [263]Previous ] + [ [261]Top ] [ [262]Contents ] [ [263]Section Contents ] [ + [264]Subsection Contents ] [ [265]Next ] [ [266]Previous ] The major difference between ANSI C and earlier C compilers is function prototyping. ANSI C allows function arguments to be checked for type @@ -1952,14 +1961,14 @@ make posix "KFLAGS=-DHDBUUCP" 9.1.3. Other Standards - [ [264]Top ] [ [265]Contents ] [ [266]Section Contents ] [ - [267]Subsection Contents ] [ [268]Next ] [ [269]Previous ] + [ [267]Top ] [ [268]Contents ] [ [269]Section Contents ] [ + [270]Subsection Contents ] [ [271]Next ] [ [272]Previous ] As the years go by, standards with-which-all-must-comply continue to pile up: AES, XPG2, XPG3, XPG4, FIPS 151-2, successive generations of POSIX, OSF/1, X/Open, Spec 1170, UNIX95, Open Group UNIX98, ISO/IEC 9945 parts 1-4, ISO 9899, 88Open, OS 99, Single Unix Specification - (SUS, [270]IEEE 1003.1-2001, not to mention "mature standards" like V7, + (SUS, [273]IEEE 1003.1-2001, not to mention "mature standards" like V7, 4.2/4.3BSD, System V R3 and R4 (SVID2 and SVID3), 4.4BSD (the basis for BSDI, OpenBSD, NetBSD, FreeBSD, Mac OS X etc), /usr/group, plus assorted seismic pronouncements of the neverending series of ephemeral @@ -1969,13 +1978,13 @@ make posix "KFLAGS=-DHDBUUCP" None of these standards simplifies life for portable applications like C-Kermit -- each one is simply one more environment to support (or circumvent, as in many cases these standards do more harm than good by - denying accesss to facilities we need, e.g. as noted in above in - [271]9.1.1). + denying access to facilities we need, e.g. as noted in above in + [274]9.1.1). 9.2. Library Issues - [ [272]Top ] [ [273]Contents ] [ [274]Section Contents ] [ - [275]Subsection Contents ] [ [276]Next ] [ [277]Previous ] + [ [275]Top ] [ [276]Contents ] [ [277]Section Contents ] [ + [278]Subsection Contents ] [ [279]Next ] [ [280]Previous ] On most modern platforms, applications are -- and often must be -- dynamically linked. This has numerous advantages (smaller executables, @@ -2001,8 +2010,8 @@ make posix "KFLAGS=-DHDBUUCP" 9.3. Unix File System Peculiarities - [ [278]Top ] [ [279]Contents ] [ [280]Section Contents ] [ [281]Next ] - [ [282]Previous ] + [ [281]Top ] [ [282]Contents ] [ [283]Section Contents ] [ [284]Next ] + [ [285]Previous ] Normally, including a BSD, System-V, POSIX, or DIRENT flag in the make entry selects the right file system code. But some versions of Unix are @@ -2048,7 +2057,7 @@ make posix "KFLAGS=-DHDBUUCP" to your makefile target. Another problem child is . Most Unix C-Kermit versions need - to #include this file from within [283]ckufio.c and [284]ckutio.c, but + to #include this file from within [286]ckufio.c and [287]ckutio.c, but some not only do not need to include it, but MUST not include it because (a) it doesn't exist, or (b) it has already been included by some other header file and it doesn't protect itself against multiple @@ -2100,12 +2109,12 @@ make posix "KFLAGS=-DHDBUUCP" attribute packet, if any. If you find that the dates are set incorrectly, you might need to build Kermit with the -DSYSUTIMEH flag, to tell it to include . If that doesn't help, look at the - code in zstrdt() in [285]ckufio.c. + code in zstrdt() in [288]ckufio.c. 9.4. Hardware Flow Control - [ [286]Top ] [ [287]Contents ] [ [288]Section Contents ] [ [289]Next ] - [ [290]Previous ] + [ [289]Top ] [ [290]Contents ] [ [291]Section Contents ] [ [292]Next ] + [ [293]Previous ] Hardware flow control is a problematic concept in many popular Unix implementations. Often it is lacking altogether, and when available, @@ -2116,7 +2125,7 @@ make posix "KFLAGS=-DHDBUUCP" b. RTS/CTS flow control support MIGHT be available for System V R3 and later if /usr/include/termiox.h exists (its successful operation also depends on the device driver, and the device itself, not to - mention the [291]cable, etc, actually supporting it). If your + mention the [294]cable, etc, actually supporting it). If your SVR3-or-later Unix system does have this file, add: -DTERMIOX @@ -2141,14 +2150,14 @@ make posix "KFLAGS=-DHDBUUCP" device name must be used. (NeXTSTEP: /dev/cufa instead of /dev/cua; IRIX: /dev/ttyf00) - See the routine tthflow() in [292]ckutio.c for details. If you find + See the routine tthflow() in [295]ckutio.c for details. If you find that your system offers hardware flow control selection under program control, you can add this capability to C-Kermit as follows: a. See if it agrees with one of the methods already used in tthflow(). if not, add new code, appropriately #ifdef'd. b. Add -DCK_RTSCTS to the compiler CFLAGS in your makefile target or - define this symbol within the appropriate #ifdefs in [293]ckcdeb.h. + define this symbol within the appropriate #ifdefs in [296]ckcdeb.h. To illustrate the difficulties with RTS/CTS, here is a tale from Jamie Watson , who added the RTS/CTS code for the RS/6000, @@ -2170,22 +2179,22 @@ make posix "KFLAGS=-DHDBUUCP" 9.5. Terminal Speeds - [ [294]Top ] [ [295]Contents ] [ [296]Section Contents ] [ [297]Next ] - [ [298]Previous ] + [ [297]Top ] [ [298]Contents ] [ [299]Section Contents ] [ [300]Next ] + [ [301]Previous ] The allowable speeds for the SET SPEED command are defined in - [299]ckcdeb.h. If your system supports speeds that are not listed in + [302]ckcdeb.h. If your system supports speeds that are not listed in "set speed ?", you can add definitions for them to ckcdeb.h. Then if the speed you are adding is one that was never used before in Kermit, such as 921600, you'll also need to add the appropriate - keywords to spdtab[] in [300]ckuus3.c, and the corresponding case to - ttsspd() in [301]ckutio.c. + keywords to spdtab[] in [303]ckuus3.c, and the corresponding case to + ttsspd() in [304]ckutio.c. 9.6. Millisecond Sleeps - [ [302]Top ] [ [303]Contents ] [ [304]Section Contents ] [ [305]Next ] - [ [306]Previous ] + [ [305]Top ] [ [306]Contents ] [ [307]Section Contents ] [ [308]Next ] + [ [309]Previous ] There is no standard for millisecond sleeps, but at least five different functions have appeared in various Unix versions that can be @@ -2214,8 +2223,8 @@ make posix "KFLAGS=-DHDBUUCP" 9.7. Nondestructive Input Buffer Peeking - [ [307]Top ] [ [308]Contents ] [ [309]Section Contents ] [ [310]Next ] - [ [311]Previous ] + [ [310]Top ] [ [311]Contents ] [ [312]Section Contents ] [ [313]Next ] + [ [314]Previous ] Some AT&T Unix versions have no way to check if input is waiting on a tty device, but this is a very important feature for Kermit. Without @@ -2255,8 +2264,8 @@ make posix "KFLAGS=-DHDBUUCP" 9.8. Other System-Dependent Features - [ [312]Top ] [ [313]Contents ] [ [314]Section Contents ] [ [315]Next ] - [ [316]Previous ] + [ [315]Top ] [ [316]Contents ] [ [317]Section Contents ] [ [318]Next ] + [ [319]Previous ] Systems with might have the symbol IEXTEN defined. This is used to turn "extended features" in the tty device driver on and off, @@ -2264,7 +2273,7 @@ make posix "KFLAGS=-DHDBUUCP" characters, etc. In most Unix implementations, it should be turned off during Kermit - operation, so if [317]ckutio.c finds this symbol, it uses it. This is + operation, so if [320]ckutio.c finds this symbol, it uses it. This is necessary, at least, on BSDI. On some systems, however, IEXTEN is either misdefined or misimplemented. The symptom is that CR, when typed to the command processor, is echoed as LF, rather than CRLF. This @@ -2278,7 +2287,7 @@ make posix "KFLAGS=-DHDBUUCP" In edits 177 and earlier, workstation users noticed a "slow screen writing" phenomenon during interactive command parsing. This was traced - to a setbuf() call in [318]ckutio.c that made console (stdout) writes + to a setbuf() call in [321]ckutio.c that made console (stdout) writes unbuffered. This setbuf() call has been there forever, and could not be removed without some risk. Kermit's operation was tested on the NeXT in edit 178 with the setbuf() call removed, and the slow-writing symptom @@ -2356,7 +2365,7 @@ make posix "KFLAGS=-DHDBUUCP" -DRENAME C-Kermit predefines the RENAME for several Unix versions in - [319]ckcdeb.h (SVR4, SUNOS41, BSD44, AIXRS, etc). You can tell if + [322]ckcdeb.h (SVR4, SUNOS41, BSD44, AIXRS, etc). You can tell if rename() is being used if the SHOW FEATURES command includes RENAME in the compiler options list. If the predefined RENAME symbol causes trouble, then add NORENAME to your CFLAGS. Trouble includes: @@ -2372,7 +2381,7 @@ make posix "KFLAGS=-DHDBUUCP" Some Unix systems (Olivetti X/OS, Amdahl UTS/V, ICL SVR3, etc) define the S_ISREG and S_ISDIR macros incorrectly. This is compensated for - automatically in [320]ckufio.c. Other systems might have this same + automatically in [323]ckufio.c. Other systems might have this same problem. If you get a compile-time error message regarding S_ISREG and/or S_ISDIR, add the following to your CFLAGS: @@ -2390,8 +2399,8 @@ make posix "KFLAGS=-DHDBUUCP" 9.9. Terminal Interruption - [ [321]Top ] [ [322]Contents ] [ [323]Section Contents ] [ [324]Next ] - [ [325]Previous ] + [ [324]Top ] [ [325]Contents ] [ [326]Section Contents ] [ [327]Next ] + [ [328]Previous ] When C-Kermit enters interactive command mode, it sets a Control-C (terminal keyboard interrupt = SIGINT) trap to allow it to return to @@ -2445,7 +2454,7 @@ make posix "KFLAGS=-DHDBUUCP" 10. DIALING OUT AND COORDINATING WITH UUCP - [ [326]Top ] [ [327]Contents ] [ [328]Next ] [ [329]Previous ] + [ [329]Top ] [ [330]Contents ] [ [331]Next ] [ [332]Previous ] The short version (general): @@ -2459,12 +2468,12 @@ make posix "KFLAGS=-DHDBUUCP" Since Red Hat 7.2, about 2002, Linux does not leave the lockfile handling to each application, but instead provides an external application, /usr/sbin/lockdev, that all applications should invoke - when they need to accesss a serial port; lockdev locks and unlocks + when they need to access a serial port; lockdev locks and unlocks the port without requiring the application to have privileges, since the privileges on the lockfile directory are assigned to lockdev. C-Kermit 8.0.211 and later support this method. But C-Kermit still needs to be able to open the port itself, and therefore if the - port's permissions do not allow read/write accesss to the general + port's permissions do not allow read/write access to the general public, the general rule must still be followed: in the most common case, it must be SETGID to the group uucp (explained below). If a pre-8.0.211 version of C-Kermit is to be installed for use with @@ -2483,14 +2492,14 @@ make posix "KFLAGS=-DHDBUUCP" Peripheral Devices => Terminals and Modems => Add Modem). Unlike most other multiuser, multitasking operating systems, Unix - allows multiple users to accesss the same serial device at the same + allows multiple users to access the same serial device at the same time, even though there is no earthly reason why two users should do this. When they do, user A will read some of the incoming characters, and user B will read the others. In all likelihood, neither user will see them all. Furthermore, User B can hang up User A's call, and so one. - Rather than change Unix to enforce exclusive accesss to serial devices + Rather than change Unix to enforce exclusive access to serial devices such as ttys, when it might still have been possible, Unix developers opted for a "lock file" mechanism. Any process that wants to open a tty device should first check to see if a file of a certain name exists, @@ -2536,7 +2545,7 @@ make posix "KFLAGS=-DHDBUUCP" * PIDs recycle. If the lockfile was created by PID 1234, which later crashed without removing the lockfile, and then a new process 1234 exists a the time the lockfile is checked, the lockfile will be - improperly taken as valid, and accesss to the device denied + improperly taken as valid, and access to the device denied unnecessarily. Several techniques address the problem of multiple names for the same @@ -2594,7 +2603,7 @@ make posix "KFLAGS=-DHDBUUCP" lockfile itself is called, and what its contents should be. In most cases, C-Kermit preprocessor flags create the appropriate configuration at compile time if the appropriate makefile target was used (see - [330]ckutio.c). The following CFLAGS options can be used to override + [333]ckutio.c). The following CFLAGS options can be used to override the built-in configuration: -DLCKDIR @@ -2679,16 +2688,16 @@ CFLAGS= -DBSD4 -DLOCK_DIR=\\\"/usr/local/locks\\\" -DNODEBUG means that you have SET CARRIER ON xx, where xx is the number of seconds to wait for carrier, and carrier did not appear within xx seconds. Solution: SET CARRIER AUTO or OFF. - b. "Sorry, accesss to lock denied." Kermit has been configured to use + b. "Sorry, access to lock denied." Kermit has been configured to use lockfiles, but (a)the lockfile directory is write-protected against - you, or (b) it does not exist. The "accesss to lock denied" message + you, or (b) it does not exist. The "access to lock denied" message will tell you the reason. If the directory does not exist, check to make sure Kermit is using the right name. Just because version n of your Unix used a certain lockfile directory is no guarantee that version n.1 does not use a different one. Workaround: ask the system administrator to install a symbolic link from the old name to the new name. Other solutions: (see below) - c. "Sorry, accesss to tty device denied." The tty device that you + c. "Sorry, access to tty device denied." The tty device that you specified in your SET LINE command is read/write protected against you. Solution: (see below) d. "Sorry, device is in use." The tty device you have specified is @@ -2726,7 +2735,7 @@ su% chmod 666 /dev/ttyXX telephone calls are not controlled -- anybody on your system can make them, without having to belong to any particular group, and this could run up your phone bill. - b. Use groups to regulate accesss. Normally the lockfile directory and + b. Use groups to regulate access. Normally the lockfile directory and and the dialout devices will have the same group (such as uucp). If so, then put everybody who's allowed to dial out into that group, and make sure that the lockfile directory and the tty devices have @@ -2739,7 +2748,7 @@ su% chmod 660 /dev/ttyXX the appropriate group (e.g. edit the /etc/group file). c. Have the superuser change Kermit to run setuid and/or setgid to the owner and/or group of the lockfile directory and the tty devices if - necessary), typically uucp (see [331]next section), but NOT root. + necessary), typically uucp (see [334]next section), but NOT root. Example: su% chown uucp kermit - or - chgrp uucp kermit @@ -2753,7 +2762,7 @@ su% chmod o+rwx /usr/spool/uucp su% chown uucp /dev/ttyXX ; chmod 600 /dev/ttyXX In some cases, the owner and group must be distinct; the key point - is that read/write accesss is required to both the UUCP lockfile + is that read/write access is required to both the UUCP lockfile directory and the tty itself. If you make C-Kermit setuid or setgid to root, it refuses to run: @@ -2765,9 +2774,9 @@ Fatal: C-Kermit setuid to root! crw-r----- 1 uucp uucp 5, 67 Feb 11 06:23 /dev/cua3 drwxrwxr-x 3 root uucp 1024 Feb 11 06:22 /var/lock - requires suid uucp to get read/write accesss on /dev/cua3 and sgid to - get read/write accesss on /var/lock (since you can't set Kermit's uid - or gid to root). + requires suid uucp to get read/write access on /dev/cua3 and sgid to + get read/write access on /var/lock (since you can't set Kermit's uid or + gid to root). The reason Kermit can't be setuid or setgid to root has to do with the fact that some Unix OS's can't switch user or group IDs in that @@ -2775,11 +2784,11 @@ drwxrwxr-x 3 root uucp 1024 Feb 11 06:22 /var/lock setgid to root means that Unix C-Kermit can't be used to make rlogin connections by non-root users. (The rlogin port is privileged, which is why the regular rlogin command is setuid root -- which is safe - because the rlogin program never has to create or accesss files like + because the rlogin program never has to create or access files like Kermit does.) For the lockfile mechanism to achieve its desired purpose -- prevention - of accesss to the same tty device by more than one process at a time -- + of access to the same tty device by more than one process at a time -- ALL programs on a given computer that open, read or write, and close tty devices must use the SAME lockfile conventions. Unfortunately, this is often not the case. Here is a typical example of how this can go @@ -2798,7 +2807,7 @@ drwxrwxr-x 3 root uucp 1024 Feb 11 06:22 /var/lock a. If there may be more than one person running Kermit at the same time, competing for the same tty device, then create a special lockfile directory just for Kermit, for example, /usr/spool/kermit, - and make sure you have read/write accesss to it. Then add the + and make sure you have read/write access to it. Then add the following to your makefile target CFLAGS, as shown earlier: -DLOCK_DIR=\\\"/usr/spool/kermit\\\" @@ -2810,7 +2819,7 @@ drwxrwxr-x 3 root uucp 1024 Feb 11 06:22 /var/lock 11. RUNNING UNIX C-KERMIT SETUID OR SETGID - [ [332]Top ] [ [333]Contents ] [ [334]Next ] [ [335]Previous ] + [ [335]Top ] [ [336]Contents ] [ [337]Next ] [ [338]Previous ] Even if you don't intend to run C-Kermit setuid, somebody else might come along and chown and chmod it after it has been built. You should @@ -2835,27 +2844,27 @@ drwxrwxr-x 3 root uucp 1024 Feb 11 06:22 /var/lock IMPORTANT NOTE: Most Unix system documentation will not give you the required information. To determine whether your Unix system supplies - the the saved-original-effective-user/group-id feature, use the - ckuuid.c program. Read and follow the instructions in the comments - at the beginning. + the saved-original-effective-user/group-id feature, use the ckuuid.c + program. Read and follow the instructions in the comments at the + beginning. C-Kermit for 4.4BSD-based systems automatically use sete[ug]id(). See - [336]ckutio.c. + [339]ckutio.c. If you have a version of Unix that is not BSD-based, but which supplies the setreuid() and setregid() functions, and these are the only way to switch between real and effective uid, add -DSETREUID to your makefile target. - WARNING: There are two calls to accesss() in [337]ckufio.c, by which + WARNING: There are two calls to access() in [340]ckufio.c, by which Kermit checks to see if it can create an output file. These calls will not work correctly when (a)you have installed C-Kermit setuid or setgid on a BSD-based Unix system, and (b) the saved-original-effective-uid/gid feature is not present, and (c) the - accesss() function always checks what it believes to be the real ID + access() function always checks what it believes to be the real ID rather than the effective ID. This is the case, for example, in Olivetti X/OS and in NeXTSTEP. In such cases, you can force correct - operation of accesss() calls by defining the symbol SW_ACC_ID at + operation of access() calls by defining the symbol SW_ACC_ID at compile time in CFLAGS. If you have a version of Unix that does not allow a process to switch @@ -2871,8 +2880,8 @@ drwxrwxr-x 3 root uucp 1024 Feb 11 06:22 /var/lock MORAL: Are you thoroughly sickened and/or frightened by all that you have just read? You should be. What is the real answer? Simple. Serial devices -- such as ttys and magnetic tapes -- in Unix should be opened - with exclusive accesss only, enforced by the Unix kernel. Shared - accesss has no conceivable purpose, legitimate or otherwise, except by + with exclusive access only, enforced by the Unix kernel. Shared access + has no conceivable purpose, legitimate or otherwise, except by privileged system programs such as getty. The original design dates from the late 1960s, when Unix was developed for laboratory use under a philosophy of trust by people within shouting distance of each other -- @@ -2881,14 +2890,14 @@ drwxrwxr-x 3 root uucp 1024 Feb 11 06:22 /var/lock emergence of Unix from the laboratory into the commercial market, we have seen every vestige of openness -- but this one -- stripped away. I'd like to see some influential Unix maker take the bold step of - making the simple kernel change required to enforce exclusive accesss - to serial devices. (Well, perhaps not so simple when bidirectionality - must also be a goal -- but then other OS's like VMS solved this problem + making the simple kernel change required to enforce exclusive access to + serial devices. (Well, perhaps not so simple when bidirectionality must + also be a goal -- but then other OS's like VMS solved this problem decades ago.) 12. CONFIGURING UNIX WORKSTATIONS - [ [338]Top ] [ [339]Contents ] [ [340]Next ] [ [341]Previous ] + [ [341]Top ] [ [342]Contents ] [ [343]Next ] [ [344]Previous ] On desktop workstations that are used by only the user at the console keyboard, C-Kermit is always used in local mode. But as delivered, @@ -2912,17 +2921,17 @@ drwxrwxr-x 3 root uucp 1024 Feb 11 06:22 /var/lock 13. BIZARRE BEHAVIOR AT RUNTIME - [ [342]Top ] [ [343]Contents ] [ [344]Next ] [ [345]Previous ] + [ [345]Top ] [ [346]Contents ] [ [347]Next ] [ [348]Previous ] See the "beware file", - [346]ckubwr.txt, for hints about runtime misbehavior. This section + [349]ckubwr.txt, for hints about runtime misbehavior. This section lists some runtime problems that can be cured by rebuilding C-Kermit. The program starts, but there is no prompt, and certain operations don't work (you see error messages like "Kermit command error in background execution"). This is because Kermit thinks it is running in - the background. See conbgt() in [347]ckutio.c. Try rebuilding Kermit + the background. See conbgt() in [350]ckutio.c. Try rebuilding Kermit with: -DPID_T=pid_t @@ -2949,7 +2958,7 @@ drwxrwxr-x 3 root uucp 1024 Feb 11 06:22 /var/lock 14. CRASHES AND CORE DUMPS - [ [348]Top ] [ [349]Contents ] [ [350]Next ] [ [351]Previous ] + [ [351]Top ] [ [352]Contents ] [ [353]Next ] [ [354]Previous ] If C-Kermit consistently dumps core at the beginning of a file transfer, look in SHOW FEATURES for CKREALPATH. If found, rebuild with @@ -3010,7 +3019,7 @@ continue 15. SYSLOGGING - [ [352]Top ] [ [353]Contents ] [ [354]Next ] [ [355]Previous ] + [ [355]Top ] [ [356]Contents ] [ [357]Next ] [ [358]Previous ] "Syslogging" means recording selected information in the system log via the Unix syslog() facility, which is available in most Unix versions. @@ -3019,7 +3028,7 @@ continue --syslog:n on the command-line, where n is a number greater than 0 to indicate the - level of syslogging. See [356]Section 4.2 of the [357]IKSD + level of syslogging. See [359]Section 4.2 of the [360]IKSD Administrator's Guide for details. Obviously you can't depend on users to include --syslog:3 (or whatever) @@ -3037,18 +3046,18 @@ make linux KFLAGS=-DSYSLOGLEVEL=2 out from your system, and to where, e.g. for security auditing. Level 2 and 3 records are equivalent to those in the connection log; - see the [358]C-Kermit 7.0 Supplement) for a detailed description of the + see the [361]C-Kermit 7.0 Supplement) for a detailed description of the connection log. 16. BUILDING SECURE VERSIONS OF C-KERMIT 8.0 - [ [359]Top ] [ [360]Contents ] [ [361]Next ] [ [362]Previous ] + [ [362]Top ] [ [363]Contents ] [ [364]Next ] [ [365]Previous ] C-Kermit 7.0 and later may be built with Kerberos(TM) and/or SRP(TM) (Secure Remote Password) and/or SSL/TLS security for strong authentication and encryption of Internet connections. These security methods require external libraries that, in their binary forms, are - restricted from export by USA law. See the [363]Kermit Security + restricted from export by USA law. See the [366]Kermit Security Reference) for details. C-Kermit binaries themselves are likewise restricted; the C-Kermit binaries that are available for public download on the Internet are not allowed to contain the security @@ -3057,7 +3066,7 @@ make linux KFLAGS=-DSYSLOGLEVEL=2 Sample makefile entries are provided for Linux and many other operating systems. A list of secure makefile entries is included in the Makefile. Complete instructions on building C-Kermit 8.0 with MIT Kerberos; - Secure Remote Password; and/or OpenSSL can be found in the [364]Kermit + Secure Remote Password; and/or OpenSSL can be found in the [367]Kermit Security Reference. SSL/TLS and Kerberos builds are increasingly problematic with the @@ -3142,7 +3151,7 @@ make netbsd+krb5+ssl \ toolsets.) Perhaps certain targets could be converted to use them, especially Linux because there are so many variations among distributions and versions. Anybody who wants to make, say, an - Autonf-based Linux target, be my guest, but bear in mind that one + Autoconf-based Linux target, be my guest, but bear in mind that one Linux target is supposed to work for all versions and distributions of Linux on all platforms. Well, one target for Linux by itself, another for Linux with OpenSSL, another for Linux with Kerberos 5, @@ -3156,14 +3165,14 @@ make netbsd+krb5+ssl \ 17. INSTALLING C-KERMIT AS AN SSH SERVER SUBSYSTEM - [ [365]Top ] [ [366]Contents ] [ [367]Previous ] + [ [368]Top ] [ [369]Contents ] [ [370]Previous ] This requires C-Kermit 8.0.206 or later and an SSH v2 server. If you list C-Kermit as a Subsystem in the SSH v2 server configuration file (as, for example, SFTP is listed), users can make SSH connections direct to a Kermit server as explained here: -[368]http://www.columbia.edu/kermit/skermit.html +[371]http://www.columbia.edu/kermit/skermit.html The name and location of the SSH server configuration file depends on your platform, which SSH product(s) you have, etc. C-Kermit itself must @@ -3191,8 +3200,8 @@ Subsystem kermit /usr/local/bin/kermit-sshsub C-Kermit would have no way of knowing that it should enter Server mode if it were not called by a special name. - [ [369]Top ] [ [370]Contents ] [ [371]C-Kermit Home ] [ [372]C-Kermit - 9.0 Overview ] [ [373]Kermit Home ] + [ [372]Top ] [ [373]Contents ] [ [374]C-Kermit Home ] [ [375]C-Kermit + 9.0 Overview ] [ [376]Kermit Home ] __________________________________________________________________ @@ -3384,193 +3393,196 @@ References 181. ftp://kermit.columbia.edu/kermit/c-kermit/ckermit80.txt 182. http://www.columbia.edu/kermit/ck60manual.html 183. http://www.columbia.edu/kermit/ckermit80.html - 184. ftp://kermit.columbia.edu/kermit/c-kermit/ckcbwr.txt - 185. http://www.columbia.edu/kermit/ckcbwr.html - 186. ftp://kermit.columbia.edu/kermit/c-kermit/ckubwr.txt - 187. http://www.columbia.edu/kermit/ckubwr.html - 188. ftp://kermit.columbia.edu/kermit/c-kermit/ckuins.txt - 189. http://www.columbia.edu/kermit/ckuins.html - 190. ftp://kermit.columbia.edu/kermit/c-kermit/ckccfg.txt - 191. http://www.columbia.edu/kermit/ckccfg.html - 192. ftp://kermit.columbia.edu/kermit/c-kermit/ckcplm.txt - 193. http://www.columbia.edu/kermit/ckcplm.html - 194. ftp://kermit.columbia.edu/kermit/c-kermit/ca_certs.pem - 195. http://www.columbia.edu/kermit/ckuins.html#x16" - 196. ftp://kermit.columbia.edu/kermit/c-kermit/makefile - 197. http://www.columbia.edu/kermit/ckuins.html#x? - 198. http://www.columbia.edu/kermit/ckuins.html#x11 - 199. http://www.columbia.edu/kermit/ckuins.html#x5.2 - 200. http://www.columbia.edu/kermit/ckermit.html#download - 201. http://www.columbia.edu/kermit/ck80binaries.html - 202. http://www.columbia.edu/kermit/ckermit.html#download - 203. http://www.columbia.edu/kermit/ckuins.html#top - 204. http://www.columbia.edu/kermit/ckuins.html#contents - 205. http://www.columbia.edu/kermit/ckuins.html#x7 - 206. http://www.columbia.edu/kermit/ckuins.html#x5 - 207. http://www.columbia.edu/kermit/ckuins.html#top - 208. http://www.columbia.edu/kermit/ckuins.html#contents - 209. http://www.columbia.edu/kermit/ckuins.html#x8 - 210. http://www.columbia.edu/kermit/ckuins.html#x6 - 211. ftp://kermit.columbia.edu/kermit/c-kermit/ckutio.c - 212. ftp://kermit.columbia.edu/kermit/c-kermit/ckutio.c - 213. http://www.columbia.edu/kermit/ckuins.html#x4.0 - 214. ftp://kermit.columbia.edu/kermit/c-kermit/ckcdeb.h - 215. ftp://kermit.columbia.edu/kermit/c-kermit/ckufio.c - 216. ftp://kermit.columbia.edu/kermit/c-kermit/ckufio.c - 217. ftp://kermit.columbia.edu/kermit/c-kermit/ckutio.c - 218. http://www.columbia.edu/kermit/ckuins.html#x10 - 219. http://www.columbia.edu/kermit/ckccfg.html#x2 - 220. http://www.columbia.edu/kermit/ckccfg.html - 221. http://www.columbia.edu/kermit/ckuins.html#x4 - 222. http://www.columbia.edu/kermit/ckuins.html#x10 - 223. ftp://kermit.columbia.edu/kermit/c-kermit/ckutio.c - 224. ftp://kermit.columbia.edu/kermit/c-kermit/ckutio.c - 225. ftp://kermit.columbia.edu/kermit/c-kermit/ckutio.c - 226. http://www.columbia.edu/kermit/ckuins.html#x9.4 - 227. mailto:kermit-support@columbia.edu - 228. http://www.columbia.edu/kermit/ckuins.html#top - 229. http://www.columbia.edu/kermit/ckuins.html#contents - 230. http://www.columbia.edu/kermit/ckuins.html#x9 - 231. http://www.columbia.edu/kermit/ckuins.html#x7 - 232. http://www.columbia.edu/kermit/ckccfg.html - 233. http://www.columbia.edu/kermit/ckccfg.html - 234. http://www.columbia.edu/kermit/ckuins.html#top - 235. http://www.columbia.edu/kermit/ckuins.html#contents - 236. http://www.columbia.edu/kermit/ckuins.html#x10 - 237. http://www.columbia.edu/kermit/ckuins.html#x8 - 238. http://www.columbia.edu/kermit/ckuins.html#x9.1 - 239. http://www.columbia.edu/kermit/ckuins.html#x9.1.1 - 240. http://www.columbia.edu/kermit/ckuins.html#x9.1.2 - 241. http://www.columbia.edu/kermit/ckuins.html#x9.1.3 - 242. http://www.columbia.edu/kermit/ckuins.html#x9.2 - 243. http://www.columbia.edu/kermit/ckuins.html#x9.3 - 244. http://www.columbia.edu/kermit/ckuins.html#x9.4 - 245. http://www.columbia.edu/kermit/ckuins.html#x9.5 - 246. http://www.columbia.edu/kermit/ckuins.html#x9.6 - 247. http://www.columbia.edu/kermit/ckuins.html#x9.7 - 248. http://www.columbia.edu/kermit/ckuins.html#x9.8 - 249. http://www.columbia.edu/kermit/ckuins.html#x9.9 - 250. ftp://kermit.columbia.edu/kermit/c-kermit/ckutio.c - 251. http://www.columbia.edu/kermit/ckuins.html#top - 252. http://www.columbia.edu/kermit/ckuins.html#x9 - 253. http://www.columbia.edu/kermit/ckuins.html#contents - 254. http://www.columbia.edu/kermit/ckuins.html#x9.2 - 255. http://www.columbia.edu/kermit/ckuins.html#x9.1.1 - 256. http://www.columbia.edu/kermit/ckuins.html#x9.1.2 - 257. http://www.columbia.edu/kermit/ckuins.html#x9.1.3 - 258. http://www.columbia.edu/kermit/ckuins.html#top - 259. http://www.columbia.edu/kermit/ckuins.html#contents - 260. http://www.columbia.edu/kermit/ckuins.html#x9 - 261. http://www.columbia.edu/kermit/ckuins.html#x9.1 - 262. http://www.columbia.edu/kermit/ckuins.html#x9.1.3 - 263. http://www.columbia.edu/kermit/ckuins.html#x9.1.1 - 264. http://www.columbia.edu/kermit/ckuins.html#top - 265. http://www.columbia.edu/kermit/ckuins.html#contents - 266. http://www.columbia.edu/kermit/ckuins.html#x9 - 267. http://www.columbia.edu/kermit/ckuins.html#x9.1 - 268. http://www.columbia.edu/kermit/ckuins.html#x9.2 - 269. http://www.columbia.edu/kermit/ckuins.html#x9.1.2 - 270. http://www.opengroup.org/onlinepubs/007904975/ - 271. http://www.columbia.edu/kermit/ckuins.html#x9.1.1 - 272. http://www.columbia.edu/kermit/ckuins.html#top - 273. http://www.columbia.edu/kermit/ckuins.html#contents - 274. http://www.columbia.edu/kermit/ckuins.html#x9 - 275. http://www.columbia.edu/kermit/ckuins.html#x9.1 - 276. http://www.columbia.edu/kermit/ckuins.html#x9.3 - 277. http://www.columbia.edu/kermit/ckuins.html#x9.1 - 278. http://www.columbia.edu/kermit/ckuins.html#top - 279. http://www.columbia.edu/kermit/ckuins.html#contents - 280. http://www.columbia.edu/kermit/ckuins.html#x9 - 281. http://www.columbia.edu/kermit/ckuins.html#x9.4 - 282. http://www.columbia.edu/kermit/ckuins.html#x9.2 - 283. ftp://kermit.columbia.edu/kermit/c-kermit/ckufio.c - 284. ftp://kermit.columbia.edu/kermit/c-kermit/ckutio.c - 285. ftp://kermit.columbia.edu/kermit/c-kermit/ckufio.c - 286. http://www.columbia.edu/kermit/ckuins.html#top - 287. http://www.columbia.edu/kermit/ckuins.html#contents - 288. http://www.columbia.edu/kermit/ckuins.html#x9 - 289. http://www.columbia.edu/kermit/ckuins.html#x9.5 - 290. http://www.columbia.edu/kermit/ckuins.html#x9.3 - 291. http://www.columbia.edu/kermit/cable.html - 292. ftp://kermit.columbia.edu/kermit/c-kermit/ckutio.c - 293. ftp://kermit.columbia.edu/kermit/c-kermit/ckcdeb.h - 294. http://www.columbia.edu/kermit/ckuins.html#top - 295. http://www.columbia.edu/kermit/ckuins.html#contents - 296. http://www.columbia.edu/kermit/ckuins.html#x9 - 297. http://www.columbia.edu/kermit/ckuins.html#x9.6 - 298. http://www.columbia.edu/kermit/ckuins.html#x9.4 - 299. ftp://kermit.columbia.edu/kermit/c-kermit/ckcdeb.h - 300. ftp://kermit.columbia.edu/kermit/c-kermit/ckuus3.c - 301. ftp://kermit.columbia.edu/kermit/c-kermit/ckutio.c - 302. http://www.columbia.edu/kermit/ckuins.html#top - 303. http://www.columbia.edu/kermit/ckuins.html#contents - 304. http://www.columbia.edu/kermit/ckuins.html#x9 - 305. http://www.columbia.edu/kermit/ckuins.html#x9.7 - 306. http://www.columbia.edu/kermit/ckuins.html#x9.5 - 307. http://www.columbia.edu/kermit/ckuins.html#top - 308. http://www.columbia.edu/kermit/ckuins.html#contents - 309. http://www.columbia.edu/kermit/ckuins.html#x9 - 310. http://www.columbia.edu/kermit/ckuins.html#x9.8 - 311. http://www.columbia.edu/kermit/ckuins.html#x9.6 - 312. http://www.columbia.edu/kermit/ckuins.html#top - 313. http://www.columbia.edu/kermit/ckuins.html#contents - 314. http://www.columbia.edu/kermit/ckuins.html#x9 - 315. http://www.columbia.edu/kermit/ckuins.html#x9.9 - 316. http://www.columbia.edu/kermit/ckuins.html#x9.7 - 317. ftp://kermit.columbia.edu/kermit/c-kermit/ckutio.c - 318. ftp://kermit.columbia.edu/kermit/c-kermit/ckutio.c - 319. ftp://kermit.columbia.edu/kermit/c-kermit/ckcdeb.h - 320. ftp://kermit.columbia.edu/kermit/c-kermit/ckufio.c - 321. http://www.columbia.edu/kermit/ckuins.html#top - 322. http://www.columbia.edu/kermit/ckuins.html#contents - 323. http://www.columbia.edu/kermit/ckuins.html#x9 - 324. http://www.columbia.edu/kermit/ckuins.html#x10 - 325. http://www.columbia.edu/kermit/ckuins.html#x9.8 - 326. http://www.columbia.edu/kermit/ckuins.html#top - 327. http://www.columbia.edu/kermit/ckuins.html#contents - 328. http://www.columbia.edu/kermit/ckuins.html#x11 - 329. http://www.columbia.edu/kermit/ckuins.html#x9 - 330. ftp://kermit.columbia.edu/kermit/c-kermit/ckutio.c + 184. ftp://kermit.columbia.edu/kermit/c-kermit/ckermit90.txt + 185. http://www.columbia.edu/kermit/ck60manual.html + 186. http://www.columbia.edu/kermit/ckermit90.html + 187. ftp://kermit.columbia.edu/kermit/c-kermit/ckcbwr.txt + 188. http://www.columbia.edu/kermit/ckcbwr.html + 189. ftp://kermit.columbia.edu/kermit/c-kermit/ckubwr.txt + 190. http://www.columbia.edu/kermit/ckubwr.html + 191. ftp://kermit.columbia.edu/kermit/c-kermit/ckuins.txt + 192. http://www.columbia.edu/kermit/ckuins.html + 193. ftp://kermit.columbia.edu/kermit/c-kermit/ckccfg.txt + 194. http://www.columbia.edu/kermit/ckccfg.html + 195. ftp://kermit.columbia.edu/kermit/c-kermit/ckcplm.txt + 196. http://www.columbia.edu/kermit/ckcplm.html + 197. ftp://kermit.columbia.edu/kermit/c-kermit/ca_certs.pem + 198. http://www.columbia.edu/kermit/ckuins.html#x16" + 199. ftp://kermit.columbia.edu/kermit/c-kermit/makefile + 200. http://www.columbia.edu/kermit/ckuins.html#x? + 201. http://www.columbia.edu/kermit/ckuins.html#x11 + 202. http://www.columbia.edu/kermit/ckuins.html#x5.2 + 203. http://www.columbia.edu/kermit/ckermit.html#download + 204. http://www.columbia.edu/kermit/ckbinaries.html + 205. http://www.columbia.edu/kermit/ckermit.html#download + 206. http://www.columbia.edu/kermit/ckuins.html#top + 207. http://www.columbia.edu/kermit/ckuins.html#contents + 208. http://www.columbia.edu/kermit/ckuins.html#x7 + 209. http://www.columbia.edu/kermit/ckuins.html#x5 + 210. http://www.columbia.edu/kermit/ckuins.html#top + 211. http://www.columbia.edu/kermit/ckuins.html#contents + 212. http://www.columbia.edu/kermit/ckuins.html#x8 + 213. http://www.columbia.edu/kermit/ckuins.html#x6 + 214. ftp://kermit.columbia.edu/kermit/c-kermit/ckutio.c + 215. ftp://kermit.columbia.edu/kermit/c-kermit/ckutio.c + 216. http://www.columbia.edu/kermit/ckuins.html#x4.0 + 217. ftp://kermit.columbia.edu/kermit/c-kermit/ckcdeb.h + 218. ftp://kermit.columbia.edu/kermit/c-kermit/ckufio.c + 219. ftp://kermit.columbia.edu/kermit/c-kermit/ckufio.c + 220. ftp://kermit.columbia.edu/kermit/c-kermit/ckutio.c + 221. http://www.columbia.edu/kermit/ckuins.html#x10 + 222. http://www.columbia.edu/kermit/ckccfg.html#x2 + 223. http://www.columbia.edu/kermit/ckccfg.html + 224. http://www.columbia.edu/kermit/ckuins.html#x4 + 225. http://www.columbia.edu/kermit/ckuins.html#x10 + 226. ftp://kermit.columbia.edu/kermit/c-kermit/ckutio.c + 227. ftp://kermit.columbia.edu/kermit/c-kermit/ckutio.c + 228. ftp://kermit.columbia.edu/kermit/c-kermit/ckutio.c + 229. http://www.columbia.edu/kermit/ckuins.html#x9.4 + 230. mailto:kermit-support@columbia.edu + 231. http://www.columbia.edu/kermit/ckuins.html#top + 232. http://www.columbia.edu/kermit/ckuins.html#contents + 233. http://www.columbia.edu/kermit/ckuins.html#x9 + 234. http://www.columbia.edu/kermit/ckuins.html#x7 + 235. http://www.columbia.edu/kermit/ckccfg.html + 236. http://www.columbia.edu/kermit/ckccfg.html + 237. http://www.columbia.edu/kermit/ckuins.html#top + 238. http://www.columbia.edu/kermit/ckuins.html#contents + 239. http://www.columbia.edu/kermit/ckuins.html#x10 + 240. http://www.columbia.edu/kermit/ckuins.html#x8 + 241. http://www.columbia.edu/kermit/ckuins.html#x9.1 + 242. http://www.columbia.edu/kermit/ckuins.html#x9.1.1 + 243. http://www.columbia.edu/kermit/ckuins.html#x9.1.2 + 244. http://www.columbia.edu/kermit/ckuins.html#x9.1.3 + 245. http://www.columbia.edu/kermit/ckuins.html#x9.2 + 246. http://www.columbia.edu/kermit/ckuins.html#x9.3 + 247. http://www.columbia.edu/kermit/ckuins.html#x9.4 + 248. http://www.columbia.edu/kermit/ckuins.html#x9.5 + 249. http://www.columbia.edu/kermit/ckuins.html#x9.6 + 250. http://www.columbia.edu/kermit/ckuins.html#x9.7 + 251. http://www.columbia.edu/kermit/ckuins.html#x9.8 + 252. http://www.columbia.edu/kermit/ckuins.html#x9.9 + 253. ftp://kermit.columbia.edu/kermit/c-kermit/ckutio.c + 254. http://www.columbia.edu/kermit/ckuins.html#top + 255. http://www.columbia.edu/kermit/ckuins.html#x9 + 256. http://www.columbia.edu/kermit/ckuins.html#contents + 257. http://www.columbia.edu/kermit/ckuins.html#x9.2 + 258. http://www.columbia.edu/kermit/ckuins.html#x9.1.1 + 259. http://www.columbia.edu/kermit/ckuins.html#x9.1.2 + 260. http://www.columbia.edu/kermit/ckuins.html#x9.1.3 + 261. http://www.columbia.edu/kermit/ckuins.html#top + 262. http://www.columbia.edu/kermit/ckuins.html#contents + 263. http://www.columbia.edu/kermit/ckuins.html#x9 + 264. http://www.columbia.edu/kermit/ckuins.html#x9.1 + 265. http://www.columbia.edu/kermit/ckuins.html#x9.1.3 + 266. http://www.columbia.edu/kermit/ckuins.html#x9.1.1 + 267. http://www.columbia.edu/kermit/ckuins.html#top + 268. http://www.columbia.edu/kermit/ckuins.html#contents + 269. http://www.columbia.edu/kermit/ckuins.html#x9 + 270. http://www.columbia.edu/kermit/ckuins.html#x9.1 + 271. http://www.columbia.edu/kermit/ckuins.html#x9.2 + 272. http://www.columbia.edu/kermit/ckuins.html#x9.1.2 + 273. http://www.opengroup.org/onlinepubs/007904975/ + 274. http://www.columbia.edu/kermit/ckuins.html#x9.1.1 + 275. http://www.columbia.edu/kermit/ckuins.html#top + 276. http://www.columbia.edu/kermit/ckuins.html#contents + 277. http://www.columbia.edu/kermit/ckuins.html#x9 + 278. http://www.columbia.edu/kermit/ckuins.html#x9.1 + 279. http://www.columbia.edu/kermit/ckuins.html#x9.3 + 280. http://www.columbia.edu/kermit/ckuins.html#x9.1 + 281. http://www.columbia.edu/kermit/ckuins.html#top + 282. http://www.columbia.edu/kermit/ckuins.html#contents + 283. http://www.columbia.edu/kermit/ckuins.html#x9 + 284. http://www.columbia.edu/kermit/ckuins.html#x9.4 + 285. http://www.columbia.edu/kermit/ckuins.html#x9.2 + 286. ftp://kermit.columbia.edu/kermit/c-kermit/ckufio.c + 287. ftp://kermit.columbia.edu/kermit/c-kermit/ckutio.c + 288. ftp://kermit.columbia.edu/kermit/c-kermit/ckufio.c + 289. http://www.columbia.edu/kermit/ckuins.html#top + 290. http://www.columbia.edu/kermit/ckuins.html#contents + 291. http://www.columbia.edu/kermit/ckuins.html#x9 + 292. http://www.columbia.edu/kermit/ckuins.html#x9.5 + 293. http://www.columbia.edu/kermit/ckuins.html#x9.3 + 294. http://www.columbia.edu/kermit/cable.html + 295. ftp://kermit.columbia.edu/kermit/c-kermit/ckutio.c + 296. ftp://kermit.columbia.edu/kermit/c-kermit/ckcdeb.h + 297. http://www.columbia.edu/kermit/ckuins.html#top + 298. http://www.columbia.edu/kermit/ckuins.html#contents + 299. http://www.columbia.edu/kermit/ckuins.html#x9 + 300. http://www.columbia.edu/kermit/ckuins.html#x9.6 + 301. http://www.columbia.edu/kermit/ckuins.html#x9.4 + 302. ftp://kermit.columbia.edu/kermit/c-kermit/ckcdeb.h + 303. ftp://kermit.columbia.edu/kermit/c-kermit/ckuus3.c + 304. ftp://kermit.columbia.edu/kermit/c-kermit/ckutio.c + 305. http://www.columbia.edu/kermit/ckuins.html#top + 306. http://www.columbia.edu/kermit/ckuins.html#contents + 307. http://www.columbia.edu/kermit/ckuins.html#x9 + 308. http://www.columbia.edu/kermit/ckuins.html#x9.7 + 309. http://www.columbia.edu/kermit/ckuins.html#x9.5 + 310. http://www.columbia.edu/kermit/ckuins.html#top + 311. http://www.columbia.edu/kermit/ckuins.html#contents + 312. http://www.columbia.edu/kermit/ckuins.html#x9 + 313. http://www.columbia.edu/kermit/ckuins.html#x9.8 + 314. http://www.columbia.edu/kermit/ckuins.html#x9.6 + 315. http://www.columbia.edu/kermit/ckuins.html#top + 316. http://www.columbia.edu/kermit/ckuins.html#contents + 317. http://www.columbia.edu/kermit/ckuins.html#x9 + 318. http://www.columbia.edu/kermit/ckuins.html#x9.9 + 319. http://www.columbia.edu/kermit/ckuins.html#x9.7 + 320. ftp://kermit.columbia.edu/kermit/c-kermit/ckutio.c + 321. ftp://kermit.columbia.edu/kermit/c-kermit/ckutio.c + 322. ftp://kermit.columbia.edu/kermit/c-kermit/ckcdeb.h + 323. ftp://kermit.columbia.edu/kermit/c-kermit/ckufio.c + 324. http://www.columbia.edu/kermit/ckuins.html#top + 325. http://www.columbia.edu/kermit/ckuins.html#contents + 326. http://www.columbia.edu/kermit/ckuins.html#x9 + 327. http://www.columbia.edu/kermit/ckuins.html#x10 + 328. http://www.columbia.edu/kermit/ckuins.html#x9.8 + 329. http://www.columbia.edu/kermit/ckuins.html#top + 330. http://www.columbia.edu/kermit/ckuins.html#contents 331. http://www.columbia.edu/kermit/ckuins.html#x11 - 332. http://www.columbia.edu/kermit/ckuins.html#top - 333. http://www.columbia.edu/kermit/ckuins.html#contents - 334. http://www.columbia.edu/kermit/ckuins.html#x12 - 335. http://www.columbia.edu/kermit/ckuins.html#x10 - 336. ftp://kermit.columbia.edu/kermit/c-kermit/ckutio.c - 337. ftp://kermit.columbia.edu/kermit/c-kermit/ckufio.c - 338. http://www.columbia.edu/kermit/ckuins.html#top - 339. http://www.columbia.edu/kermit/ckuins.html#contents - 340. http://www.columbia.edu/kermit/ckuins.html#x13 - 341. http://www.columbia.edu/kermit/ckuins.html#x11 - 342. http://www.columbia.edu/kermit/ckuins.html#top - 343. http://www.columbia.edu/kermit/ckuins.html#contents - 344. http://www.columbia.edu/kermit/ckuins.html#x14 - 345. http://www.columbia.edu/kermit/ckuins.html#x12 - 346. ftp://kermit.columbia.edu/kermit/c-kermit/ckubwr.txt - 347. ftp://kermit.columbia.edu/kermit/c-kermit/ckutio.c - 348. http://www.columbia.edu/kermit/ckuins.html#top - 349. http://www.columbia.edu/kermit/ckuins.html#contents - 350. http://www.columbia.edu/kermit/ckuins.html#x15 - 351. http://www.columbia.edu/kermit/ckuins.html#x13 - 352. http://www.columbia.edu/kermit/ckuins.html#top - 353. http://www.columbia.edu/kermit/ckuins.html#contents - 354. http://www.columbia.edu/kermit/ckuins.html#x16 - 355. http://www.columbia.edu/kermit/ckuins.html#x14 - 356. http://www.columbia.edu/kermit/uiksd.html#x4.2 - 357. http://www.columbia.edu/kermit/uiksd.html - 358. http://www.columbia.edu/kermit/ckermit2.html - 359. http://www.columbia.edu/kermit/ckuins.html#top - 360. http://www.columbia.edu/kermit/ckuins.html#contents - 361. http://www.columbia.edu/kermit/ckuins.html#x17 - 362. http://www.columbia.edu/kermit/ckuins.html#x15 - 363. http://www.columbia.edu/kermit/security.html - 364. http://www.columbia.edu/kermit/security80.html - 365. http://www.columbia.edu/kermit/ckuins.html#top - 366. http://www.columbia.edu/kermit/ckuins.html#contents - 367. http://www.columbia.edu/kermit/ckuins.html#x16 - 368. http://www.columbia.edu/kermit/skermit.html - 369. http://www.columbia.edu/kermit/ckuins.html#top - 370. http://www.columbia.edu/kermit/ckuins.html#contents - 371. http://www.columbia.edu/kermit/ckermit.html - 372. http://www.columbia.edu/kermit/ck90updates.html - 373. http://www.columbia.edu/kermit/index.html + 332. http://www.columbia.edu/kermit/ckuins.html#x9 + 333. ftp://kermit.columbia.edu/kermit/c-kermit/ckutio.c + 334. http://www.columbia.edu/kermit/ckuins.html#x11 + 335. http://www.columbia.edu/kermit/ckuins.html#top + 336. http://www.columbia.edu/kermit/ckuins.html#contents + 337. http://www.columbia.edu/kermit/ckuins.html#x12 + 338. http://www.columbia.edu/kermit/ckuins.html#x10 + 339. ftp://kermit.columbia.edu/kermit/c-kermit/ckutio.c + 340. ftp://kermit.columbia.edu/kermit/c-kermit/ckufio.c + 341. http://www.columbia.edu/kermit/ckuins.html#top + 342. http://www.columbia.edu/kermit/ckuins.html#contents + 343. http://www.columbia.edu/kermit/ckuins.html#x13 + 344. http://www.columbia.edu/kermit/ckuins.html#x11 + 345. http://www.columbia.edu/kermit/ckuins.html#top + 346. http://www.columbia.edu/kermit/ckuins.html#contents + 347. http://www.columbia.edu/kermit/ckuins.html#x14 + 348. http://www.columbia.edu/kermit/ckuins.html#x12 + 349. ftp://kermit.columbia.edu/kermit/c-kermit/ckubwr.txt + 350. ftp://kermit.columbia.edu/kermit/c-kermit/ckutio.c + 351. http://www.columbia.edu/kermit/ckuins.html#top + 352. http://www.columbia.edu/kermit/ckuins.html#contents + 353. http://www.columbia.edu/kermit/ckuins.html#x15 + 354. http://www.columbia.edu/kermit/ckuins.html#x13 + 355. http://www.columbia.edu/kermit/ckuins.html#top + 356. http://www.columbia.edu/kermit/ckuins.html#contents + 357. http://www.columbia.edu/kermit/ckuins.html#x16 + 358. http://www.columbia.edu/kermit/ckuins.html#x14 + 359. http://www.columbia.edu/kermit/uiksd.html#x4.2 + 360. http://www.columbia.edu/kermit/uiksd.html + 361. http://www.columbia.edu/kermit/ckermit2.html + 362. http://www.columbia.edu/kermit/ckuins.html#top + 363. http://www.columbia.edu/kermit/ckuins.html#contents + 364. http://www.columbia.edu/kermit/ckuins.html#x17 + 365. http://www.columbia.edu/kermit/ckuins.html#x15 + 366. http://www.columbia.edu/kermit/security.html + 367. http://www.columbia.edu/kermit/security80.html + 368. http://www.columbia.edu/kermit/ckuins.html#top + 369. http://www.columbia.edu/kermit/ckuins.html#contents + 370. http://www.columbia.edu/kermit/ckuins.html#x16 + 371. http://www.columbia.edu/kermit/skermit.html + 372. http://www.columbia.edu/kermit/ckuins.html#top + 373. http://www.columbia.edu/kermit/ckuins.html#contents + 374. http://www.columbia.edu/kermit/ckermit.html + 375. http://www.columbia.edu/kermit/ck90updates.html + 376. http://www.columbia.edu/kermit/index.html diff --git a/ckuker.nr b/ckuker.nr index f85a3d6..03b30e7 100644 --- a/ckuker.nr +++ b/ckuker.nr @@ -1,4 +1,4 @@ -.\" @(#) kermit.1 9.0.301 2011/07/11 Columbia University +.\" @(#) kermit.1 9.0.302 2011/08/20 Columbia University .TH KERMIT 1 "JULY 2011" "User Manuals" .na .SH NAME diff --git a/ckutio.c b/ckutio.c index 6551e77..05564de 100644 --- a/ckutio.c +++ b/ckutio.c @@ -1,12 +1,12 @@ #define CKUTIO_C #ifdef aegis -char *ckxv = "Aegis Communications support, 9.0.324, 20 June 2011"; +char *ckxv = "Aegis Communications support, 9.0.326, 20 August 2011"; #else #ifdef Plan9 -char *ckxv = "Plan 9 Communications support, 9.0.324, 20 June 2011"; +char *ckxv = "Plan 9 Communications support, 9.0.326, 20 August 2011"; #else -char *ckxv = "UNIX Communications support, 9.0.324, 20 June 2011"; +char *ckxv = "UNIX Communications support, 9.0.326, 20 August 2011"; #endif /* Plan9 */ #endif /* aegis */ @@ -50,7 +50,13 @@ extern int duplex; #endif /* CK_ANSIC */ #endif /* OSF13 */ -#include /* System error numbers */ +#ifndef HPUXPRE65 +#include /* Error number symbols */ +#else +#ifndef ERRNO_INCLUDED +#include /* Error number symbols */ +#endif /* ERRNO_INCLUDED */ +#endif /* HPUXPRE65 */ #ifdef __386BSD__ #define ENOTCONN 57 @@ -4970,6 +4976,9 @@ ttlock(ttdev) char *ttdev; { int x, n; int islink = 0; +#ifdef __FreeBSD__ + char *devname; +#endif /* __FreeBSD__ */ #ifdef NOUUCP debug(F100,"ttlock NOUUCP","",0); @@ -4981,8 +4990,17 @@ ttlock(ttdev) char *ttdev; { #ifdef USETTYLOCK haslock = 0; /* Not locked yet. */ *flfnam = '\0'; /* Lockfile name is empty. */ +#ifdef __FreeBSD__ + if ((devname = xxlast(ttdev,'/')) != NULL) +#ifdef FREEBSD8 + ckstrncat(lockname,devname+1,DEVNAMLEN-ckstrncpy(lockname,"pts",4)); +#else + ckstrncpy(lockname,devname+1,DEVNAMLEN); +#endif /* FREEBSD8 */ +#else if (!strncmp(ttdev,"/dev/",5) && ttdev[5]) ckstrncpy(lockname,ttdev+5,DEVNAMLEN); +#endif /* __FreeBSD__ */ else ckstrncpy(lockname,ttdev,DEVNAMLEN); /* diff --git a/ckututor.txt b/ckututor.txt index b54942d..ef2aebe 100644 --- a/ckututor.txt +++ b/ckututor.txt @@ -480,9 +480,9 @@ Command Files, Macros, and Scripts One way to have the macro definition in effect is to type the definition at the Kermit prompt. Another way is to store the definition - in a file and TAKE the file. If you want the the definition to be in - effect automatically every time you start Kermit, put the definition in - your initialization or customization file (explained [78]below). + in a file and TAKE the file. If you want the definition to be in effect + automatically every time you start Kermit, put the definition in your + initialization or customization file (explained [78]below). Here's a somewhat more ambitious example: @@ -1011,7 +1011,7 @@ MAKING CONNECTIONS to its prompt automatically when you log out from the remote computer or the connection is otherwise lost. - You can also dial from a modem that is accesssible by Telnet, + You can also dial from a modem that is accessible by Telnet, e.g. to a reverse terminal server. In this case the command sequence is: @@ -1359,7 +1359,7 @@ KERMIT CLIENT/SERVER CONNECTIONS There are dozens -- maybe hundreds -- of other commands, described in the built-in help, on the website, and/or in the published or online - manuals. But even if you don't have accesss to documentation, you can + manuals. But even if you don't have access to documentation, you can "set locus remote" and then use pretty much the same commands you would use with any FTP client. diff --git a/ckuus5.c b/ckuus5.c index d542de3..c4c8782 100644 --- a/ckuus5.c +++ b/ckuus5.c @@ -10770,6 +10770,15 @@ initoptlist() { #ifdef __FreeBSD__ makestr(&(optlist[noptlist++]),"__FreeBSD__"); #endif /* __FreeBSD__ */ +#ifdef FREEBSD4 + makestr(&(optlist[noptlist++]),"FREEBSD4"); +#endif /* FREEBSD4 */ +#ifdef FREEBSD8 + makestr(&(optlist[noptlist++]),"FREEBSD8"); +#endif /* FREEBSD8 */ +#ifdef FREEBSD9 + makestr(&(optlist[noptlist++]),"FREEBSD9"); +#endif /* FREEBSD9 */ #ifdef __linux__ makestr(&(optlist[noptlist++]),"__linux__"); #endif /* __linux__ */ diff --git a/makefile b/makefile index ddd0cd4..9efe262 100644 --- a/makefile +++ b/makefile @@ -1,8 +1,8 @@ # makefile / Makefile / ckuker.mak / CKUKER.MAK # -# Mon Jul 11 09:24:25 2011 -BUILDID=20110711 -CKVER= "9.0.301" +# Sun Aug 21 10:33:08 2011 +BUILDID=20110821 +CKVER= "9.0.302" # # -- Makefile to build C-Kermit for UNIX and UNIX-like platforms -- # @@ -22,13 +22,16 @@ CKVER= "9.0.301" # Note: Author is no longer at Columbia University or at the 115th Street # address effective 1 July 2011. The email address should still work, # as well as the website and FTP addresses, for the foreseeable future. +# For new developments, also check: +# +# http://www.columbia.edu/~fdc/kermit/ # # Contributions from many others. Special thanks to Jeff Altman for the # secure-build targets, Peter Eichhorn, assyst GmbH, for the consolidated # HP-UX targets and the "uninstall" target, to Robert Lipe for the updated # and consolidated SCO UNIX / ODT / OSR5 targets, to Ric Anderson for the # IRIX 6.x targets, to Seth Theriault for major improvements to the -# Mac OS X targets. +# Mac OS X targets, and to Alexey Dokuchaev for FreeBSD 9.0. # # C-Kermit is written and produced by hand without any automated procedures # such as autoconf / automake / configure, although some of the targets below @@ -53,10 +56,10 @@ CKVER= "9.0.301" # separated by whitespace. Some versions of "make" understand these as # directives. Uppercase letters remove the danger, e.g. "# If you have..." # -# WARNING: This is a huge makefile. Although -# this is less likely since the turn of the century, some "make" programs -# might run out of memory. If this happens to you, edit away the parts that -# do not apply to your platform and try again. +# WARNING: This is a huge makefile. Although this is less likely since the +# turn of the century, some "make" programs might run out of memory. If this +# happens to you, edit away the parts that do not apply to your platform and +# try again. # # WARNING 2: In many cases this file invokes itself recursively, sometimes # several levels deep (as in the Linux targets); i.e. some targets are used @@ -132,6 +135,10 @@ CKVER= "9.0.301" # + "make netbsd+ssl", NetBSD with OpenSSL 0.9.7 or later. # + "make netbsd+krb5", NetBSD with Kerberos 5. # + "make netbsd+krb5+ssl", NetBSD with Kerberos 5 and OpenSSL 0.9.7 or later. +# ? "make freebsd1" for FreeBSD 1.x +# ? "make freebsd2" for FreeBSD 2.x +# + "make freebsd3" for FreeBSD 3.x +# ? "make freebsd4" for FreeBSD 4.0 # + "make freebsd", FreeBSD 4.1 or later. # + "make freebsd+ssl", FreeBSD 5.0 or later with OpenSSL 0.9.7 or later. # + "make openbsd", OpenBSD 2.3 or later. @@ -1705,6 +1712,7 @@ freebsd2c: #FreeBSD 3.x with ncurses and uu_lock() #(Note: uu_lock() goes back to 2.2.2, but not necessarily 2.0) +#OK 2011/08/20 FreeBSD 3.3 freebsd3: @echo 'Making C-Kermit $(CKVER) for FreeBSD 3.x with ncurses...' $(MAKE) CC=$(CC) CC2=$(CC2) xermit KTARGET=$${KTARGET:-$(@)} \ @@ -1734,27 +1742,61 @@ freebsd40: #FreeBSD 4.1 and above #Like FreeBSD 4.0 but without the NONOSETBUF hack and with CK_NEWTERM. -#OK 2011/06/15 FreeBSD 3.3, 4,4, 4.7, and 8.2 -freebsd freebsd41 freebsd72: +#NOTE: This target definitely does not work for FreeBSD 3.3 in 9.0.302. +#and it has not been tested on 4 or 5. +#OK 2011/06/xx FreeBSD 3.3, 4,4, 4.7, and 8.2 +#OK 2011/08/21 FreeBSD 3.3, 4.4, 6.4, 9.0 +freebsd freebsd41 freebsd72 freebsd5 freebsd6 freebsd7 freebsd8 freebsd9: @echo 'Making C-Kermit $(CKVER) for FreeBSD 4.1 or later...' + @if test `uname -r | cut -d . -f 1` -ge 8; then \ + HAVE_FBSD8='-DFREEBSD8'; \ + else HAVE_FBSD8=''; fi; \ + if test `uname -r | cut -d . -f 1` -ge 9; then \ + HAVE_FBSD9='-DFREEBSD9'; \ + else HAVE_FBSD9=''; fi; \ + if test -f /usr/include/utmpx.h ; \ + then HAVE_UTMPX='-DHAVEUTMPX' ; \ + else HAVE_UTMPX='' ; fi; \ $(MAKE) CC=$(CC) CC2=$(CC2) xermit KTARGET=$${KTARGET:-$(@)} \ "CFLAGS= -DBSD44 -DCK_NCURSES -DCK_NEWTERM -DTCPSOCKET -DNOCOTFMC \ - -DFREEBSD4 -DUSE_UU_LOCK -DFNFLOAT \ - -DHERALD=\"\\\" `uname` `uname -r`\\\"\" \ - -funsigned-char -DTPUTSARGTYPE=int -DUSE_STRERROR $(KFLAGS) -O -pipe" \ + -DFREEBSD4 $$HAVE_FBSD8 $$HAVE_FBSD9 -DUSE_UU_LOCK -DFNFLOAT \ + $$HAVE_UTMPX -DHERALD=\"\\\" `uname -rs`\\\"\" \ + -funsigned-char -DTPUTSARGTYPE=int -DUSE_STRERROR $(KFLAGS) \ + -O2 -pipe"\ "LIBS= -lncurses -lcrypt -lutil -lm $(LIBS)" -#FreeBSD 5.0 or later with OpenSSL 0.9.7 or later. +#FreeBSD 5.0 or later with OpenSSL. #OK 2011/06/15 FreeBSD 4.7 and 8.2 +#OK 2011/08/20 FreeBSD 9.0-CURRENT freebsd+ssl freebsd+openssl freebsd50+openssl: - @echo 'Making C-Kermit $(CKVER) for FreeBSD 5.0, ncurses, openssl' - $(MAKE) CC=$(CC) CC2=$(CC2) xermit KTARGET=$${KTARGET:-$(@)} \ - "CFLAGS= -DBSD44 -DCK_NCURSES -DCK_NEWTERM -DTCPSOCKET -DNOCOTFMC \ - -DCK_AUTHENTICATION -DCK_SSL $(SSLINC) -DZLIB \ - -DFREEBSD4 -DUSE_UU_LOCK -DFNFLOAT -funsigned-char -DTPUTSARGTYPE=int \ - -DFREEBSD41 -DFREEBSD42 -DFREEBSD43 -DFREEBSD44 -DFREEBSD45 \ - -DFREEBSD46 -DFREEBSD50 -DUSE_STRERROR $(KFLAGS) -O -pipe" \ - "LIBS= -lncurses -lcrypt -lssl -lcrypto -lutil -lm $(SSLLIB) $(LIBS)" + @echo 'Making C-Kermit $(CKVER) for FreeBSD with Kerberos 5...' + @case `openssl version` in \ + *0.9.7*) OPENSSLOPTION="-DOPENSSL_097" ;; \ + *0.9.8*) OPENSSLOPTION="-DOPENSSL_098" ;; \ + *1.[0-9].[0-9]*) OPENSSLOPTION="-DOPENSSL_100" ;; \ + *) OPENSSLOPTION="" ;; \ + esac; \ + HAVE_DES=''; \ + DES_LIB=''; \ + if ls /usr/lib/libdes* > /dev/null 2> /dev/null || \ + ls $(SSLLIB)/libdes* > /dev/null 2> /dev/null; then \ + DES_LIB='-ldes'; \ + HAVE_DES='-DCK_DES -DLIBDES'; \ + echo "HAVE DES"; \ + else echo "NO DES"; \ + fi; \ + $(MAKE) freebsd KTARGET=$${KTARGET:-$(@)} "CC = $(CC)" "CC2 = $(CC2)" \ + KFLAGS="-DCK_AUTHENTICATION -DCK_SSL $(SSLINC) -DZLIB $$OPENSSLOPTION \ + $$HAVE_DES $(KFLAGS)" "LNKFLAGS = $(LNKFLAGS)" \ + "LIBS= -lncurses -lcrypt -lssl -lcrypto -lutil -lm \ + $(SSLLIB) $$DES_LIB $(LIBS)"; \ + if [ ! -f ./wermit ] || [ ./ckcmai.o -nt ./wermit ] ; then \ + echo ""; \ + echo "If build failed try:"; \ + echo ""; \ + echo " make clean ; make $${KTARGET:-$(@)} KFLAGS=-UCK_DES"; \ + echo ""; \ + fi #NetBSD 1.4.1 or later with vanity banner automated with uname #and automatic inclusion of large file support if it is available. @@ -1763,6 +1805,7 @@ freebsd+ssl freebsd+openssl freebsd50+openssl: #disabled on ckcfn2.c ("KFLAGS=-O0") (Letter O Digit Zero). #(This could be automated by testing `uname -m` for "sun3".) #OK: 2011/06/15 on NetBSD 1.5.2 and 5.1. +#OK: 2011/08/21 on 5.1. netbsd netbsd2 netbsd15 netbsd16 old-netbsd: @echo Making C-Kermit $(CKVER) for NetBSD with curses... $(MAKE) CC=$(CC) CC2=$(CC2) xermit KTARGET=$${KTARGET:-$(@)} \ @@ -1775,6 +1818,7 @@ netbsd netbsd2 netbsd15 netbsd16 old-netbsd: #NetBSD 1.4.1 or later with OpenSSL #OK: 2011/06/15 on NetBSD 5.1 (but not 1.5.2 with OpenSSL 0.9.5a) +#OK: 2011/08/21 on 5.1. netbsd+ssl netbsd+openssl: @echo 'Making C-Kermit $(CKVER) for NetBSD+OpenSSL SSLLIB=$(SSLLIB)' @case `openssl version` in \ @@ -1792,7 +1836,7 @@ netbsd+ssl netbsd+openssl: echo "HAVE DES"; \ else echo "NO DES"; \ fi; \ - $(MAKE) netbsd KTARGET=$${KTARGET:-$(@)} "CC = gcc" "CC2 = gcc" \ + $(MAKE) netbsd KTARGET=$${KTARGET:-$(@)} "CC = $(CC)" "CC2 = $(CC2)" \ "KFLAGS= -DCK_AUTHENTICATION -DCK_ENCRYPTION -DCK_CAST $$HAVE_DES \ -DCK_SSL -DCK_PAM -DZLIB -DNO_DCL_INET_ATON $$OPENSSLOPTION \ $(KFLAGS)" "LNKFLAGS = $(LNKFLAGS)" \ @@ -1802,9 +1846,9 @@ netbsd+ssl netbsd+openssl: #NetBSD with MIT Kerberos 5: # OK 2011/06/15 (once K5INC and K5LIB were set right). # NOT OK for Heimdal - Heimdal Kerberos support in C-Kermit needs work. +# OK: 2011/08/21 on 5.1. netbsd+krb5: @echo 'Making C-Kermit $(CKVER) for NetBSD with Kerberos 5...' - @echo 'Making C-Kermit $(CKVER) for NetBSD+OpenSSL+Kerberos5...' @case `openssl version` in \ *0.9.7*) OPENSSLOPTION="-DOPENSSL_097" ;; \ *0.9.8*) OPENSSLOPTION="-DOPENSSL_098" ;; \ @@ -1820,7 +1864,7 @@ netbsd+krb5: echo "HAVE DES"; \ else echo "NO DES"; \ fi; \ - $(MAKE) netbsd KTARGET=$${KTARGET:-$(@)} "CC = gcc" "CC2 = gcc" \ + $(MAKE) netbsd KTARGET=$${KTARGET:-$(@)} "CC = $(CC)" "CC2 = $(CC2)" \ "KFLAGS= -DCK_AUTHENTICATION -DCK_ENCRYPTION -DCK_KERBEROS -DKRB5 \ -DCK_CAST $$HAVE_DES -DNOFTP_GSSAPI $(K5INC) $(K5INC)/krb5 \ $(KFLAGS)" \ @@ -1828,7 +1872,7 @@ netbsd+krb5: -lcrypto -lgssapi -lkrb5 -lm -lutil $(LIBS)" # NetBSD - With Kerberos 5 and SSL and Zlib. -# OK 2011/06/15 +# OK: 2011/08/21 on 5.1 with MIT Kerberos. netbsd+krb5+ssl netbsd+krb5+openssl+zlib: @echo 'Making C-Kermit $(CKVER) for NetBSD+OpenSSL+Kerberos5...' @case `openssl version` in \ @@ -1846,7 +1890,7 @@ netbsd+krb5+ssl netbsd+krb5+openssl+zlib: echo "HAVE DES"; \ else echo "NO DES"; \ fi; \ - $(MAKE) netbsd KTARGET=$${KTARGET:-$(@)} "CC = gcc" "CC2 = gcc" \ + $(MAKE) netbsd KTARGET=$${KTARGET:-$(@)} "CC = $(CC)" "CC2 = $(CC2)" \ "KFLAGS= -DCK_AUTHENTICATION -DCK_ENCRYPTION -DCK_CAST $$HAVE_DES \ -DCK_KERBEROS -DKRB5 -DNOFTP_GSSAPI $(K5INC) $(K5INC)/krb5 \ -DCK_SSL -DCK_PAM -DZLIB -DNO_DCL_INET_ATON $$OPENSSLOPTION \ @@ -1907,6 +1951,8 @@ openbsdold: # -DUSE_UU_LOCK and -lutil added for uu_lock() # -DNDSYSERRLIST changed to -DUSE_STRERROR #If this gives you trouble use the previous entry. +#NOTE: The openbsd and openbsd+ssl should be reworked to be like the +#corresponding FreeBSD and NetBSD targets. The mirbsd targets should openbsd: @echo Making C-Kermit $(CKVER) for OpenBSD 2.3 or later... $(MAKE) CC=$(CC) CC2=$(CC2) xermit KTARGET=$${KTARGET:-$(@)} \ @@ -3803,12 +3849,30 @@ solaris9g+krb5+krb4: -lkrb4 -lcrypto -lgssapi_krb5 -lkrb5 -lcom_err -lk5crypto \ -ldes $(LIBS)" -#Solaris 9 with gcc + Kerberos 5. -#Columbia Only - libdes has a version number in its name. -#In the general case, change -ldes425 to -des. -#If you have Kerberos 1.4 or later and and krb5_init_ets can't be found -#at link time, add -DNO_KRB5_INIT_ETS. -cu-solaris9g+krb5: +#Solaris 9, 10, or 11 with gcc... +#Uses streams PTYs rather than BSD ptys as in C-Kermit 8.0 and earlier. +#This target is chained to be the secure solaris9g+xxx targets below. +solaris9g solaris10g solaris11g: + @echo 'Making C-Kermit $(CKVER) for Solaris 9 or later with gcc' + @case `uname -r` in \ + 5.9) SOLARISVERSION="-DSOLARIS9" ;; \ + 5.10) SOLARISVERSION="-DSOLARIS10" ;; \ + 5.11) SOLARISVERSION="-DSOLARIS11" ;; \ + *) SOLARISVERSION="-DSOLARIS" ;; \ + esac ; \ + $(MAKE) "MAKE=$(MAKE)" CC="gcc -m32" CC2="gcc -m32" xermit \ + KTARGET=$${KTARGET:-$(@)} \ + "CFLAGS = -g -O -Usun -DSVR4 $$SOLARISVERSION -DUSE_STRERROR \ + -DSTERMIOX -DSELECT -DFNFLOAT -DCK_PAM -DCK_SHADOW -funsigned-char \ + -DHAVE_STREAMS -DHAVE_GRANTPT -DHAVE_PTSNAME -DPUSH_PTEM \ + -DPUSH_LDTERM -DPUSH_TTCOMPAT \ + -DCK_CURSES -DCK_NEWTERM -DDIRENT -DHDBUUCP -DTCPSOCKET \ + -D_FILE_OFFSET_BITS=64 $(KFLAGS)" \ + "LIBS= -ltermlib -lsocket -lnsl -lm -lresolv -lpam $(LIBS)" + +#Solaris 9, 10, or 11 with gcc + Kerberos 5 + OpenSSL. +#OK C-Kermit 9.0.301. +solaris9g+krb5+ssl solaris10g+krb5+ssl solaris11g+krb5+ssl: @case `openssl version` in \ *0.9.7*) OPENSSLOPTION="-DOPENSSL_097" ;; \ *0.9.8*) OPENSSLOPTION="-DOPENSSL_098" ;; \ @@ -3833,49 +3897,13 @@ cu-solaris9g+krb5: $(MAKE) xermit KTARGET=$${KTARGET:-$(@)} CC=gcc CC2=gcc \ "CFLAGS = -O -Usun -DSVR4 -DSOLARIS9 -DSTERMIOX -DSELECT -DFNFLOAT \ -DCK_CURSES -DCK_NEWTERM -DDIRENT -DHDBUUCP -DTCPSOCKET -DBIGBUFOK \ - -DCK_AUTHENTICATION -DCK_KERBEROS -DKRB5 -DCK_ENCRYPTION -DCK_CAST \ - $$OPENSSLOPTION $$HAVE_DES $(K5INC) $(K5INC)/krb5 $(KFLAGS)" \ - "LIBS= $(K5LIB) -ltermlib -lsocket -lnsl -lm -lresolv -lcrypto \ + -DCK_AUTHENTICATION -DCK_SSL -DZLIB -DCK_KERBEROS -DKRB5 \ + -DCK_ENCRYPTION -DCK_CAST $$OPENSSLOPTION \ + $$HAVE_DES $(SSLINC) $(K5INC) $(K5INC)/krb5 $(KFLAGS)" \ + "LIBS= $(SSLLIB) $(K5LIB) -lz -lssl -ltermlib -lsocket -lnsl -lm \ + -lresolv -lcrypto \ $$GSSAPILIB -lkrb5 -lcom_err -lk5crypto $$DES_LIB $(LIBS)" -#Solaris 9 with gcc + OpenSSL + Kerberos 5 + Krb4 + Shadow + Long files -#Columbia Only, mainly because of the -R clause. -# (I tried adding -DCK_SRP and -lsrp but got a lot of symbol referencing -# errors at link time.) -cu-solaris9g+krb5+krb4+openssl+shadow+pam+zlib: - $(MAKE) xermit KTARGET=$${KTARGET:-$(@)} CC=gcc CC2=gcc \ - "CFLAGS = -O -Usun -DSVR4 -DSOLARIS -DSTERMIOX -DSELECT -DFNFLOAT \ - -DSOLARIS9 -D_FILE_OFFSET_BITS=64 -DBIGBUFOK \ - -DCK_CURSES -DCK_NEWTERM -DDIRENT -DHDBUUCP -DTCPSOCKET \ - -DCK_AUTHENTICATION -DCK_KERBEROS -DKRB5 -DKRB4 -DKRB524 \ - -DCK_ENCRYPTION -DCK_SSL -DCK_DES -DCK_CAST -DNO_KRB5_INIT_ETS \ - -DZLIB -DCK_PAM -DCK_SHADOW -DLIBDES -DOPENSSL_097 -DCK_FORWARD_X \ - $(K5INC) $(K5INC)/krb5 $(SSLINC) $(KFLAGS)" \ - "LIBS= $(K5LIB) $(SSLLIB) -R/opt/local/lib -ltermlib -lsocket -lnsl \ - -lm -lresolv -lkrb4 -lssl -lcrypto -lgssapi_krb5 -lkrb5 \ - -lcom_err -lk5crypto -lpam -ldes425 -lz $(LIBS)" - -#Solaris 9, 10, or 11 with gcc... -#Uses streams PTYs rather than BSD ptys as in C-Kermit 8.0 and earlier. -#This target is chained to be the secure solaris9g+xxx targets below. -solaris9g solaris10g solaris11g: - @echo 'Making C-Kermit $(CKVER) for Solaris 9 or later with gcc' - @case `uname -r` in \ - 5.9) SOLARISVERSION="-DSOLARIS9" ;; \ - 5.10) SOLARISVERSION="-DSOLARIS10" ;; \ - 5.11) SOLARISVERSION="-DSOLARIS11" ;; \ - *) SOLARISVERSION="-DSOLARIS" ;; \ - esac ; \ - $(MAKE) "MAKE=$(MAKE)" CC="gcc -m32" CC2="gcc -m32" xermit \ - KTARGET=$${KTARGET:-$(@)} \ - "CFLAGS = -g -O -Usun -DSVR4 $$SOLARISVERSION -DUSE_STRERROR \ - -DSTERMIOX -DSELECT -DFNFLOAT -DCK_PAM -DCK_SHADOW -funsigned-char \ - -DHAVE_STREAMS -DHAVE_GRANTPT -DHAVE_PTSNAME -DPUSH_PTEM \ - -DPUSH_LDTERM -DPUSH_TTCOMPAT \ - -DCK_CURSES -DCK_NEWTERM -DDIRENT -DHDBUUCP -DTCPSOCKET \ - -D_FILE_OFFSET_BITS=64 $(KFLAGS)" \ - "LIBS= -ltermlib -lsocket -lnsl -lm -lresolv -lpam $(LIBS)" - #Solaris 9, 10, or 11 with gcc, 64 bit build. #Peeking inside FILE struct not allowed in 64-bit world. #DON'T USE THIS ONE ON PC ARCHITECTURE - It compiles and links but won't run. @@ -3901,7 +3929,7 @@ solaris9g64 solaris10g64 solaris11g64: #Solaris 9, 10, or 11 with SunPro CC #Uses streams PTYs rather than BSD ptys as in C-Kermit 8.0 and earlier. #This target is chained to by the secure targets below. -#OK: 2011/06/15 +#OK C-Kermit 9.0 solaris9 solaris10 solaris11: @echo 'Making C-Kermit $(CKVER) for Solaris 9 or later with Sun CC' @case `uname -r` in \ @@ -3929,7 +3957,7 @@ solaris9 solaris10 solaris11: # Don't use 'make -e' because that inhibits passing of KFLAGS to # the base (solaris9) target. # -#OK: 2011/06/14 +#OK C-Kermit 9.0 solaris9+ssl solaris10+ssl solaris11+ssl \ solaris9+openssl solaris10+openssl solaris11+openssl: @echo 'Making C-Kermit $(CKVER) for Solaris 9/10/11 with OpenSSL: cc' @@ -3957,7 +3985,7 @@ solaris9+openssl solaris10+openssl solaris11+openssl: # chains to the solaris{9,10,11}g target but for some reason it doesn't work if # you add the -DFORWARD_X option, thus the solaris9g+openssl+forward_x target. # -#OK: 2020/06/15 +#OK: 2011/06/14 solaris9g+ssl solaris10g+ssl solaris11g+ssl \ solaris9g+openssl solaris10g+openssl solaris11g+openssl: @echo 'Making C-Kermit $(CKVER) for Solaris 9/10/11 with OpenSSL: gcc' @@ -5342,7 +5370,7 @@ hpux0500: "CFLAGS = -DHPUX -DHPUX5 -DHPUXPRE65 -DNOREDIRECT -DDCLGETCWD \ -DNOGETUSERSHELL -DNOGFTIMER -DNOSYSLOG -DNOTOMACROS -DNOLSTAT \ -DNOSYMLINK -DNOINITGROUPS -DNOUNICODE -DNOLEARN -DNOLONGLONG \ - $(KFLAGS)" "LIBS = $(LIBS)" "LNKFLAGS = " + -DVOID=int -DCKVOID=int $(KFLAGS)" "LIBS = $(LIBS)" "LNKFLAGS = " #HP-9000 500 HP-UX 5.21 with Wollongong WIN/TCP 1.2 TCP/IP. #Requires /usr/wins/usr/include and /usr/lib/libnet.a from Wollongong. @@ -5352,9 +5380,9 @@ hpux0500: hpux0500wintcp: @MESSAGE1="with WIN/TCP but without any extra compiler optimization" \ $(MAKE) hpux0500 KTARGET=$${KTARGET:-$(@)} \ - "KFLAGS = -DTCPSOCKET -DHPUX5WINTCP -DINADDRX -DNO_DNS_SRV -DNOMHHOST \ - -DNOHADDRLIST -DNOLONGLONG -I/usr/wins/usr/include $(KFLAGS)" \ - "LIBS = /usr/lib/libnet.a" + "KFLAGS = -DTCPSOCKET -DHPUX5WINTCP -DINADDRX -DNO_DNS_SRV \ + -DNOMHHOST -DVOID=int -DCKVOID=int -DNOHADDRLIST -DNOLONGLONG \ + -I/usr/wins/usr/include $(KFLAGS)" "LIBS = /usr/lib/libnet.a" #HP-UX 6.5, short filenames, no network and no curses support. #ckcpro, ckuusr, ckuus3 and others are broken out because they make the @@ -6170,9 +6198,11 @@ linux+krb5: K5CRYPTO=''; \ if ls /lib/libk5crypto* > /dev/null 2> /dev/null; then \ K5CRYPTO='-lk5crypto'; \ + else if ls /usr/lib/libk5crypto* > /dev/null 2> /dev/null; then \ + K5CRYPTO='-lk5crypto'; \ else if ls /usr/lib64/libk5crypto* > /dev/null 2> /dev/null; then \ K5CRYPTO='-lk5crypto'; \ - fi; fi; \ + fi; fi; fi; \ COM_ERR=''; \ if ls /lib/libcom_err* > /dev/null 2> /dev/null; then \ COM_ERR='-lcom_err'; \ @@ -6275,9 +6305,11 @@ linux+krb5+ssl linux+krb5+openssl: K5CRYPTO=''; \ if ls /lib/libk5crypto* > /dev/null 2> /dev/null; then \ K5CRYPTO='-lk5crypto'; \ + else if ls /usr/lib/libk5crypto* > /dev/null 2> /dev/null; then \ + K5CRYPTO='-lk5crypto'; \ else if ls /usr/lib64/libk5crypto* > /dev/null 2> /dev/null; then \ K5CRYPTO='-lk5crypto'; \ - fi; fi; \ + fi; fi; fi; \ COM_ERR=''; \ if ls /lib/libcom_err* > /dev/null 2> /dev/null; then \ COM_ERR='-lcom_err'; \ -- 2.11.0