home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!noc.near.net!hri.com!enterpoop.mit.edu!eru.mt.luth.se!lunic!sunic!corax.udac.uu.se!corax.udac.uu.se!ewerlid
- From: ewerlid@ida.docs.uu.se (Ove Ewerlid)
- Newsgroups: comp.os.linux
- Subject: Re: Problems with telnet
- Message-ID: <EWERLID.92Dec22081718@ida.docs.uu.se>
- Date: 22 Dec 92 07:17:18 GMT
- References: <1992Dec21.100349.24896@solaris.rz.tu-clausthal.de>
- Organization: University of Uppsala, Sweden
- Lines: 20
- NNTP-Posting-Host: ida.csd.uu.se
- In-reply-to: gobbi@sg1502.chemie.uni-marburg.de's message of Mon, 21 Dec 1992 10:03:49 GMT
-
-
- I haven't got a solution for the telnet problem.
- If you can use REMOTE SHELL (rsh) instead you may have a workaround.
- (Btw, I use the 3c503 (Etherlink II Adapter 2227) driver,
- the rsh comes from SLS and kernel is 0.99.1 (was once 0.99))
-
- I use something like this:
-
- rsh xterm-host-name 'xterm -d my-linux-box-name:0.0' &
-
- to get a nice xterm on the linux-box X-display.
- Haven't had any problems with hangups.
-
- (Ofcourse, you must have a proper .rhost file on the host where you
- run the xterm and that may not be acceptable to you wrt security.)
-
- The only (?) remaining problems are that the incoming data rate
- is as low as 3-4 kb/s (outgoing is 200kb/s) and that an incoming tcp/ip
- connection sometimes can time out if it is subject to high data rates.
- (This is receiving/sending data from a sparc2.)
-