🚀 go-pugleaf

In article <BvEFu2.8xI@cs.vu.nl> mjh@cs.vu.nl (Huisjes MJ) writes:
>For some reason when you do a rlogin, the rlogind on the other side does
>not set your controlling tty.

>This happens in both NS 2.x and NS 3.0.
>
>This is a bug isn't it ?

Yes, it's a bug.  And it's a bug that's been known for a long time.
The fix for 2.x is available by anonymous ftp from sutro.sfsu.edu
[130.212.15.230] as pub/2.0-fixed-rlogind.tar.Z

I haven't investigated the behavior under 3.0, but I'm not the
least bit surprised to hear of yet-another-known-but-unfixed-bug
in the networking software.  3.0 seems to have quite a lot of
them, and NeXT neither seems interested in rectifying the
situation nor releasing the relevant sources to allow others to
do so.  Fortunately, I'm in no hurry to "upgrade," and in our
heterogeneous/multivendor environment, I can easily find a non-
NeXT machine where the bundled software works the way it's
supposed to (and the /usr/include files haven't been bulldozed,
in case I really do need to recompile something from the
publicly-available sources).

"Really looking forward to 3.1"  (yeah, right)

					-=EPS=-