Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!elroy.jpl.nasa.gov!ncar!tank!gargoyle!ddsw1!nvk
From: nvk@ddsw1.MCS.COM (Norman Kohn)
Newsgroups: comp.unix.i386
Subject: Re: commport boards and MNP/etc (was: Error-correcting modems & uucp
Message-ID: <1990Apr13.000550.7767@ddsw1.MCS.COM>
Date: 13 Apr 90 00:05:50 GMT
References: <963@frcs.UUCP> <21466@nuchat.UUCP> <511445@nstar.UUCP> <1990Apr8.154834.1545@ddsw1.MCS.COM> <630@gvlv2.GVL.Unisys.COM> <1990Apr11.164509.4045@ddsw1.MCS.COM>
Reply-To: nvk@ddsw1.MCS.COM (Norman Kohn)
Organization: ddsw1.MCS.COM Contributor, Mundelein, IL
Lines: 20

In article <1990Apr11.164509.4045@ddsw1.MCS.COM> karl@mcs.MCS.COM (Karl Denninger) writes:
...
>One question:
>
>If you're using ISC, or AT&T, or ESIX Unix, there is NO IOCTL to turn on and
>off hardware flow control!
>
>That is, there is no way to command the board to enable it, unless the board
>vendor has inserted some hack (read: external command) to do so on a
>port-by-port or (much worse) board-by-board basis.

Digoboard does this via a "ditty" program, with syntax
resembling stty and options of (-)ctsflow and (-)rtsflow


-- 
Norman Kohn   		| ...ddsw1!nvk
Chicago, Il.		| days/ans svc: (312) 650-6840
			| eves: (312) 373-0564