home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!elroy.jpl.nasa.gov!ucla-cs!rutgers!uwvax!cs.wisc.edu!cole
- From: cole@dip.cs.wisc.edu (Bruce Cole)
- Newsgroups: comp.unix.ultrix
- Subject: Re: Ultrix 4.2 rlogin somewhat broken
- Message-ID: <cole.716591033@cs.wisc.edu>
- Date: 15 Sep 92 21:03:53 GMT
- References: <1992Sep12.070314.23900@jarvis.csri.toronto.edu> <60286@mimsy.umd.edu> <cole.716523393@cs.wisc.edu> <1992Sep15.072449.21372@alcatel.ch>
- Sender: news@cs.wisc.edu (The News)
- Organization: U of Wisconsin Madison - Computer Sciences
- Lines: 19
-
- vannes@srzts304.alcatel.ch (Tom van Nes) writes:
- >Why recompile the kernel? get BSD rlogin source.
-
- You must not have understood my message. There is a kernel bug which
- causes Ultrix machines to not handle out of band data as expected. Even
- with a BSD version of rlogin, you can still have this problem. When I first
- encountered this problem, I was using a BSD version of rlogin. As long as
- your rlogin program still uses out of band data, you should be interested
- in having your kernel fixed. Because the kernel bug involves
- a time dependency, different versions of rlogin might affect the probability
- in which you encounter the problem. This time dependency explains why
- DEC's sleep(1) change to the rlogind program can make difference.
-
- Blindly reinstalling your rlogin program until it works for you is not
- a good fix.
- --
- Bruce Cole
- Computer Sciences Department
- U. of Wisconsin - Madison
-