From: Jeffrey Altman <jaltman@columbia.edu>
To: Corey Minyard <minyard@acm.org>
Cc: Peter Astrand <peter@cendio.se>,
ltsp-discuss@lists.sourceforge.net, d.sbragion@infotecna.it,
linux-serial@vger.kernel.org
Subject: Re: Serial port redirection
Date: Thu, 04 Dec 2003 12:52:36 -0500 [thread overview]
Message-ID: <3FCF7464.9030000@columbia.edu> (raw)
In-Reply-To: <3FCDE8FC.3070400@acm.org>
[-- Attachment #1: Type: text/plain, Size: 1010 bytes --]
Corey Minyard wrote:
> Jeffrey Altman wrote:
>
>> The reality is RFC is experimental and not authoritative. The only
>> thing that really counts is what Cisco actually shipped in their IOS
>> implementation. Lucky me I actually have a terminal
>> server that implements it. If you look at the C-Kermit sources you
>> will see that the client is written to accept both values from the
>> server. You will also find that Cisco does not send the baudrates as
>> specified in the RFC but instead uses an enumeration.
>
>
> True. But if I had been lucky and had a terminal server, I would not
> have written ser2net :).
>
> So Cisco uses a enumeration? Do you think it is possible to make them
> compatible and do both in ser2net, or is it a non-issue?
Clients can use heuristics to determine which should be used. Servers
must choose one; but I would make a configurable option.
(The clock is off by one day 4 hours and 12 minutes. This causes your
e-mail to get lost way down in my queue.)
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3427 bytes --]
next prev parent reply other threads:[~2003-12-04 17:52 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
[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 [this message]
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=3FCF7464.9030000@columbia.edu \
--to=jaltman@columbia.edu \
--cc=d.sbragion@infotecna.it \
--cc=linux-serial@vger.kernel.org \
--cc=ltsp-discuss@lists.sourceforge.net \
--cc=minyard@acm.org \
--cc=peter@cendio.se \
/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