From: hank@Blimp (Hendrik G. Seliger) Subject: Re: net-0.2 stuff (and presumebly SLS net stuff) Date: 12 Feb 1993 16:22:38 GMT
waltje@metallica.uwalt.nl.mugnet.org (Fred N. van Kempen) writes:
: sadkins@bigbird.cs.ohiou.edu (Scott W. Adkins) wrote:
:
: I am the official NET maintainer for LINUX, so here goes:
:
: > 1) rlogin into the linux box works fine, but when trying to rlogin out,
: > the connection is closed before even seeing a login prompt on the remote
: > system. Why is rlogin broken? I have heard that other people have had
: > this problem as well, and I am not the only one. So, how many people
: > out there have this problem?
: This is a problem of the kernel not handling TCP Urgent Data correctly.
: It has been fixed in 0.99.4 and up. Just recompile the NET binaries of
: telnet[d] and rlogin[d], and you're off.
:
Well, I'm sorry to tell you that I'm not off!! I just recompiled the
stuff (I'm using 0.99-p5). rlogin still works from linux to linux or
from another system into the linux box, but I don't get out. Up to
recompilation the connection was just closed, now I even get a messy
message:
> Kite:45~> rlogin ulla
> rlogin: read: I/O error.
> Alarm clock
> Kite:46~> rlogin: connection closed.
Kite is the linux system, ulla a sparc. The sources I use are from
SLS-s1-disk. There seems to more to this.
Hank.