From: Jeffrey Altman <jaltman-WLbs8XpHrcb2fBVCVOL8/A@public.gmane.org>
To: Corey Minyard <minyard-HInyCGIudOg@public.gmane.org>
Cc: Peter Astrand <peter-+4tYiAq3b6azQB+pC5nmwQ@public.gmane.org>,
ltsp-discuss-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
d.sbragion-eDKEdzQQoQ4L5bzFcGmneg@public.gmane.org,
linux-serial-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Serial port redirection
Date: Thu, 04 Dec 2003 12:13:49 -0500 [thread overview]
Message-ID: <3FCF6B4D.2050103@columbia.edu> (raw)
In-Reply-To: <3FCDDEE6.4070905-HInyCGIudOg@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 895 bytes --]
Corey Minyard wrote:
> Jeffrey Altman wrote:
>
>> Its not a Kermit bug; If you pass the socket file descriptor to an
>> external program
>> the external program must understand telnet protocol. Otherwise, it
>> can't send the
>> correct data format.
>
>
> No, it *is* a kermit bug. When kermit sends an 0xff character, it
> needs to escape it per the standard telnet protocol. It's obviously
> not doing this.
>
> -Corey
I agree, the IAC must be quoted. The problem is that when an external
protocol handler is
executed as a child process, Kermit is suspended and the child process
has complete control
over the socket file descriptor.
Kermit is not sitting between the external protocol and the host.
Some versions of sz have a command line flag to handle this situation
such that IAC (0xff) are
not sent but are instead escaped within the zmodem protocol.
Jeffrey Altman
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3427 bytes --]
next prev parent reply other threads:[~2003-12-04 17:13 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-01 14:32 Serial port redirection Peter Astrand
[not found] ` <Pine.LNX.4.44.0312011300480.8142-100000-K9BqGu7AvB3wj5YHdwD3Ga2PxDmRETKR@public.gmane.org>
2003-12-03 16:30 ` Peter Astrand
2003-12-03 13:31 ` Corey Minyard
2003-12-05 9:11 ` Peter Astrand
2003-12-05 21:10 ` Corey Minyard
2003-12-08 9:49 ` Peter Astrand
2003-12-08 10:11 ` Peter Astrand
[not found] ` <Pine.LNX.4.44.0312031557190.12826-100000-K9BqGu7AvB3wj5YHdwD3Ga2PxDmRETKR@public.gmane.org>
2003-12-03 16:36 ` Jeffrey Altman
[not found] ` <3FCE1101.40502-WLbs8XpHrcb2fBVCVOL8/A@public.gmane.org>
2003-12-03 13:02 ` Corey Minyard
[not found] ` <3FCDDEE6.4070905-HInyCGIudOg@public.gmane.org>
2003-12-04 17:13 ` Jeffrey Altman [this message]
[not found] ` <3FCF6B4D.2050103-WLbs8XpHrcb2fBVCVOL8/A@public.gmane.org>
2003-12-03 13:23 ` Corey Minyard
2003-12-04 17:37 ` Jeffrey Altman
2003-12-04 17:49 ` Corey Minyard
[not found] ` <3FCF73BE.1010707-HInyCGIudOg@public.gmane.org>
2003-12-04 19:12 ` Jeffrey Altman
2003-12-03 16:42 ` Jeffrey Altman
2003-12-03 13:21 ` Corey Minyard
2003-12-04 17:34 ` Jeffrey Altman
[not found] ` <3FCF7026.6070109-WLbs8XpHrcb2fBVCVOL8/A@public.gmane.org>
2003-12-03 13:45 ` Corey Minyard
2003-12-04 17:52 ` Jeffrey Altman
2003-12-05 9:19 ` Peter Astrand
2003-12-05 15:33 ` Jeffrey Altman
2003-12-05 15:43 ` Peter Astrand
2003-12-05 15:50 ` Jeffrey Altman
2003-12-06 23:31 ` Peter Astrand
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3FCF6B4D.2050103@columbia.edu \
--to=jaltman-wlbs8xphrcb2fbvcvol8/a@public.gmane.org \
--cc=d.sbragion-eDKEdzQQoQ4L5bzFcGmneg@public.gmane.org \
--cc=linux-serial-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ltsp-discuss-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=minyard-HInyCGIudOg@public.gmane.org \
--cc=peter-+4tYiAq3b6azQB+pC5nmwQ@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox