public inbox for linux-serial@vger.kernel.org
 help / color / mirror / Atom feed
From: Corey Minyard <minyard@acm.org>
To: Jeffrey Altman <jaltman@columbia.edu>
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 11:49:50 -0600	[thread overview]
Message-ID: <3FCF73BE.1010707@acm.org> (raw)
In-Reply-To: <3FCF70E0.4000302@columbia.edu>

It would be fairly trivial to write such a program, though.  You could 
pass it the actual program you want, and it could make the protocol 
transparent.

-Corey

Jeffrey Altman wrote:

> Ideally that would be true.  However, the mechanisms for doing so are 
> not portable to all platforms on which C-Kermit still compiles.  
> Please remember that C-Kermit works on platforms that existed before 
> "select()" was invented.
>
> Jeffrey Altman
>
>
> Corey Minyard wrote:
>
>> Ah, I missed that.  Ideally, something (i would think kermit) should 
>> sit between the program and the socket to make it transparent.  But 
>> yes, I see what you are saying.
>>
>> Thanks,
>>
>> -Corey
>>



  reply	other threads:[~2003-12-04 17:49 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 [this message]
     [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=3FCF73BE.1010707@acm.org \
    --to=minyard@acm.org \
    --cc=d.sbragion@infotecna.it \
    --cc=jaltman@columbia.edu \
    --cc=linux-serial@vger.kernel.org \
    --cc=ltsp-discuss@lists.sourceforge.net \
    --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