rfarris@rfengr.com (Rick Farris) (04/08/91)
Having just installed tcp/ip between my SCO Unix 3.2v2.0 system and my SCO Open Desktop 1.1 system, I'm learning a lot about network operation. One think I haven't learned, though, is how to turn off flow-control for an rlogin session. In particular, I'd like to be able to use ^S and ^Q in emacs, as God intended. I've tried various combinations of "stty -ixon" on each end of the connection, to no avail. If I telnet across flow control is disabled, but when I rlogin, I just can't shake it. Any ideas?
orava@robocop.hut.fi (Petri Wessman) (04/12/91)
On 8 Apr 91 06:20:02 GMT, rfarris@rfengr.com (Rick Farris) said: Rick> Having just installed tcp/ip between my SCO Unix 3.2v2.0 Rick> system and my SCO Open Desktop 1.1 system, I'm learning a Rick> lot about network operation. Rick> One think I haven't learned, though, is how to turn off Rick> flow-control for an rlogin session. In particular, I'd like Rick> to be able to use ^S and ^Q in emacs, as God intended. If someone has a solution, please tell me too. SCO TC/IP is *broken* in a big way, emacs (and other packages) are a pain to use when SCO braindeadism refuses to deal with flow control in the proper way (i.e. ignore it when the other endpoint goes into raw mode). To add insult to injury, the local SCO dealer thinks it's a feature and not a bug! Grrrr.... P.S. Maybe I'm getting all wound up over nothing, and there is a simple way to get it to Do The Right Thing, but have R all the FM I could find haven't found a solution yet. //Petri
jim@newmedia.UUCP (Jim Beveridge) (04/12/91)
In article <1991Apr08.062002.20072@rfengr.com>, rfarris@rfengr.com (Rick Farris) writes: > One think I haven't learned, though, is how to turn off > flow-control for an rlogin session. In particular, I'd like > to be able to use ^S and ^Q in emacs, as God intended. > > I've tried various combinations of "stty -ixon" on each end > of the connection, to no avail. I reported this as a bug to SCO way back in the Open Desktop beta release. SCO gave the typical "mollify the customer" answer about it not being possible for one reason or another. We did not find a workaround. On a related note: --> Flame on <-- I just received ODT 1.1. I am strongly tempted to return it. Many of the bugs that were problems back in the beta release are STILL BUGS (at least now they are documented). I now have job control that won't work because most of the software doesn't support it. I still can't properly support the rest of my BSD systems because I don't have YP (excuse me, NIS). I still can't use 256 colors in X. It works just fine in Microsoft Windows 3.0. Another of the problems I reported back in the beta release, that of the DOS/X-Sight/Mouse interaction, was noted fixed in the photocopied readme document, it wasn't even in early enough to make the release note booklet. My bug report was 1 1/2 years ago. If they put half as much time and effort into development as they do into full page ads in magazines they might create a pretty decent product. I am really tired of waiting for SCO to fix bugs. This is one site that won't be purchasing any more SCO products. --> set coolant on <-- Jim