Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!eos!labrea!decwrl!sun!pitstop!sundc!seismo!uunet!mcvax!prlb2!kulcs!dannyb From: dannyb@kulcs.uucp (Danny Backx) Newsgroups: comp.sys.ibm.pc.rt Subject: Re: Inquieries for "Bad Aspects" of the RT Message-ID: <139@icarus.kulcs.uucp> Date: 5 Dec 88 13:32:27 GMT References: <7963@dasys1.UUCP> <301@itcatl.UUCP> Reply-To: dannyb@kulcs.UUCP (Danny Backx) Organization: Katholieke Universiteit Leuven, Dept. Computer Science Lines: 34 In article <301@itcatl.UUCP> robin@itcatl.UUCP (Robin Cutshaw) writes: >AIX: > 2.1.X was a joke. Many, many bugs. 2.2 fixed most of the bugs >and added many new and wonderful features (rlogin, rwhod, etc). I Indeed. I routinely use a telnet connection to work with an RT. This was absolutely impossible with 2.1.2. I think the Ethernet software was broken. (AIX 2.2 is better, but still not good.) What happens on 2.2: when a large amount of data is being sent to my terminal, (say the output of 'ls -l /etc'), the first part gets tru, then the output stops, and after a LONG time, it continues (also in bursts). I suspect the timeout strategy in TCP. In 2.1.2, the first burst got tru, and then after some time the telnet connection broke. (Logging me out...) Rlogin is slightly better than telnet (don't ask why), but I can't use vi with it. > [..] . If you rlogin from a non AIX environment, >vi won't work (a bug in their curses support). A workaround is to >rlogin back into yourself (potentially dangerous these days) and it >will fix itself. As mentioned, vi doesn't work in an rlogin session. It does under telnet. I tried your workaround, but it didn't work for me. -- Danny -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Danny Backx | mail: Danny Backx Tel: +32 16 200656 x 3544 | Katholieke Universiteit Leuven Fax: +32 16 205308 | Dept. Computer Science E-mail: dannyb@kulcs.UUCP | Celestijnenlaan 200 A ... mcvax!prlb2!kulcs!dannyb | B-3030 Leuven dannyb@blekul60.BITNET | Belgium