From: sand@milton.u.washington.edu (Derek Upham)
Subject: Re: Questions: tip, src install problems, kermit, rz, crypt library
Organization: University of Washington
Date: Fri, 31 Jul 1992 05:24:03 GMT

pfaffman@pilot.njin.net (Jay Pfaffman) writes:

>I managed to get tip to work, but what term type do I tell the Sun I'm
>using?  What are those "last message received XXX times" errors about?

The terminal type is "pc3".  The description should be in
/usr/share/misc/termcap, and most termcaps should have the similar
"pc".  I don't know what's causing the kernel diagnostics, but see
below...

>Anybody got kermit 5a (?) going?  Is the vt10[02] emulation good?
>Is there a better term program?  MS-Kermit is very nice, but I hope to
>be leaving that behind.

Kermit 5A (with a binary) is included in the etc01 distribution.  It
has no vt10[02] emulation---the plan was, people would use "screen"
(also included in the etc01 distribution) for emulation.  This works,
mostly, but there is a known bug in "screen" that forces you to hit ^V
twice to send it.  See the thread (started about two days ago,
something like "sockets bug? ^V as an escape character?") to find more
information.

>rz gets *lots* of checksum errors with my 9600 modem.  The modem is
>doing error correction, so that I don't think *that's* the problem.
>Is BSD too slow to keep up?  Will a 16550 (?) UART help?

My V.32bis/V.42/V.42bis modem (with a 16550A UART) was dropping
characters under Linux, due to a problem with the COM driver code.
Lowering my DTE from 38,400bps to 19,200bps solved the problem.
386BSD has even worse problems over dialup lines, and fiddling with
the DTE doesn't seem to help.  I'm pretty sure (thanks to Linux) that
the problem isn't with the remote machine, the remote modem, or my
modem.  This leaves the 386BSD COM drivers (and this might also
explain the periodic kernel messages).  I suspect there are bugs
somewhere in the two levels of terminal emulation, as well.

>extract complained that it couldn't find src01.install.  Why not?
>Should I worry?  Why isn't extract a script so that I can fix it when
>it breaks?

Use "extract" for the bin01 stuff.  Don't bother with it for anything
else.  Just put all the src01 files in /root, then cd to / and run

  cat /root/src01.?? | uncompress | cpio -div

If there's anything wrong with the files (like an extra 0xff character
on the end of two pieces...) uncompress will barf on the stream.
Plus, you can taunt this command at will.  If you value your sanity,
don't extact from the /tmp directory, or store any the files there.
The /etc/rc shell script automatically clears /tmp on boot.  You can
lose eight hours worth of files in an instant.

>I understand why a real crypt wasn't included, but Linux has one.
>Shouldn't it be easy to plug it in?  What will have to be recompiled
>besides login, su, & passwd? (crypt, I guess:-)

Chris Demetriou (sp?) posted something about encrypted passwords a
while back.  I'm sure someone has it saved online.

>Jay Pfaffman, Computer Coordinator        pfaffman@pilot.njin.net
>Dwight-Englewood School, 315 E. Palisade Ave.                      
>Englewood, NJ  07631-0489                 201-569-9500
-- 
Derek Lynn Upham                                     University of Washington
sand@u.washington.edu                University Computing Services Operations
=============================================================================
"Ha!  Your Leaping Tiger Kung Fu is no match for my Frightened Piglet Style!"
Newsgroups: comp.unix.bsd