"Pennell, David" wrote:

> > * setting line parameters (other than the common ones like
> > data rate, input/output flow control, xon/xoff chars, stop bits,
> > data bits, and parity)
> >
> > * changing line parameters on an open port
> >
> > * flushing input or output without closing the port
> >
> > * detecting break signals, or parity or framing errors
> >
> > * sending breaks
> >
> > * error reporting (how is this handled generally? I don't see
> > any easy way to pass back errno...)
> >
> > * reading or setting modem control line states (beyond DTR,
> > maybe DCD, and RTS/CTS) (or waiting for change in their status)
> 
> If you start on this, please consider the possibility that you
> might want to perform most of these operations via different
> mechanisms than ioctl() or stty.  For instance, most of these
> operations are supported by various RFC's that extend Telnet.
> I know of at least one terminal server that supports them (and
> lots of folks that try to drive remote consoles through them).
> It would be slick to be able to use Squeak instead of Expect.

I don't understand. I'm dealing with real, physical serial ports.
The only way I can get them to do the above things is via ioctl()
or the termios routines (on Linux, anyway).

I thought Telnet was over IP...

-- 
Ned Konz
currently: Stanwood, WA
email:     ned at bike-nomad.com
homepage:  http://bike-nomad.com