Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!convex!convex!convex!cs.utexas.edu!geraldo.cc.utexas.edu!sylvester.cc.utexas.edu!not-for-mail From: vax@sylvester.cc.utexas.edu (Vax) Newsgroups: comp.os.386bsd.questions Subject: Re: Slcompress -- enforce HW flow-control, patch Date: 7 Jul 1993 16:35:00 -0500 Organization: The University of Texas - Austin Lines: 19 Message-ID: <21ffi4$i46@sylvester.cc.utexas.edu> References: <hastyC9IFM3.F9u@netcom.com> <BLYMN.93Jul6170320@mallee.awadi.com.au> <21f6er$2v7@max.in-berlin.de> NNTP-Posting-Host: sylvester.cc.utexas.edu In article <21f6er$2v7@max.in-berlin.de> berry@max.IN-Berlin.DE (Stefan Behrens) writes: > >I also recommend the usage of hardware flow-control on the serial port. >But why change every application to support it. I simply hacked the >kernel to force usage of hardware flow-control configurable with the >minor device nuber. > Is it just me, or can someone just use stty to enable flow control on the line? I thought that's what it is for. NOTE: rctsrts flag is not documented on stty :-) I think the preponderance of device files is a bit ugly, and it can eliminate the usefulness of file locks in /var/lock/LCK..* ; if you have two names for the same device the locks are not mutex. However, this has hardly stopped Unix hackers in the past; maybe it's not as big an issue to other people. When stty exits, does it restore the line to its default condition? What else do I have to know about stty to get it to act properly on a tty line? -- Protect our endangered bandwidth - reply by email. NO BIG SIGS! VaX#n8 vax@ccwf.cc.utexas.edu - finger for more info if you even care.