Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!xlink.net!math.fu-berlin.de!irz401!uriah!not-for-mail
From: j@bonnie.tcd-dresden.de (J Wunsch)
Newsgroups: comp.os.386bsd.misc
Subject: Re: Interpretation of text as a command by communications software
Date: 5 Nov 1993 19:01:47 +0100
Organization: Textil Computer Design GmbH Dresden, Germany
Lines: 30
Message-ID: <2be4ebINN5de@bonnie.tcd-dresden.de>
References: <CFp30p.AHH@mv.mv.com>
NNTP-Posting-Host: bonnie.tcd-dresden.de
Keywords: communications, terminal, zmodem, SZ, 386BSD, Crosstalk
kaikow@mv.mv.com (Howard Kaikow) writes:
>Crosstalk appears to have a "feature" that is rather annoying. It is unclear
>to me where this is documented.
...
>Much to my astonishment, when I then did an ls -la, zmodem got invoked on
>my PC when the ls -la got to the file named rz!!!
>Does this imply that it is something on the unix side interpreting the
>bytes on the terminal as a command? Seems rather messy, but interesting.
Certainly not. The unix side does not interpret anything from its output,
totally sure there. Obviously, your communication's program is brain-dead
enough to interpret it. Instead of bothering with the more complicated sz
transmission start sequence, they obviously tend to interpret the string
"rz" in some context (e.g., if there's no leading and trailing alphabetic
character, or if there's a trailing newline). Instead of ls -l, try an
"echo *", where the filenames are all on a single line (so that your rz
file hopefully is not the last one and thus not followed by a newline).
Or use another dos prog...
Btw., i'm sometimes using sz/rz between unix machines without any bad side
effects as you've described.
--
in real life: J"org Wunsch | ) o o | primary: joerg_wunsch@tcd-dresden.de
above 1.8 MHz: DL 8 DTL | ) | | private: joerg_wunsch@uriah.sax.de
| . * ) == |
``An elephant is a mouse with an operating system.''