From: Andrej Borsenkow <borsenkow.msk@sni.de>
To: Zsh users mailing list <zsh-users@math.gatech.edu>
Cc: "Timothy J. Luoma" <luomat@peak.org>
Subject: Re: problem from NeXTStep 3.3 rlogin to SunOS 4.1.4
Date: Wed, 5 Mar 1997 09:47:12 +0300 (MSK) [thread overview]
Message-ID: <Pine.SV4.3.95.970305093821.4589C-100000@itsrm1.mow.sni.de> (raw)
In-Reply-To: <199703041904.OAA03868@kira.peak.org>
On Tue, 4 Mar 1997, Timothy J. Luoma wrote:
>
> When I rlogin to my SUN account from my NeXT, I have been "losing"
> output. Most often it happens with 'ls' or 'cat' where the command
> runs but nothing comes to the screen. If I feed it to 'less' that
> works.
>
I can only confirm, that it happens. It happens with _rlogin_ (and not
with _rsh_). It is not limited to NeXT. I have two SVR4 based systems -
one is based on original SVR4.0.3 for i386 (SINIX-L), other on DC/OSx from
Pyramid (SINIX-N).
rlogin SINIX-N -> SINIX-L works O.K.
rlogin SINIX-L -> SINIX-N shows the above problem. It is not always the
whole output lost - sometimes I see only the first line of `ls' output;
sometimes the `CR NL' after prompt is lost, that is:
% ls
results in
% ls....... (first line of ls output).
It seems to depend on output size - `ls -l' have no problems.
`cat' OTOH works.
I actually have no clues, except supposing some bugs in system. If anybody
have the ideas, how this could be debugged - much thanks in advance.
greetings
-------------------------------------------------------------------------
Andrej Borsenkow Fax: +7 (095) 252 01 05
SNI ITS Moscow Tel: +7 (095) 252 13 88
NERV: borsenkow.msk E-Mail: borsenkow.msk@sni.de
-------------------------------------------------------------------------
next prev parent reply other threads:[~1997-03-05 7:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-03-04 19:04 Timothy J. Luoma
1997-03-04 22:20 ` Bart Schaefer
1997-03-05 6:47 ` Andrej Borsenkow [this message]
1997-03-05 15:54 ` Zoltan T. Hidvegi
1997-03-05 16:09 ` Andrej Borsenkow
1997-03-05 17:39 ` Bart Schaefer
1997-03-05 16:45 ` Timothy Luoma
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.SV4.3.95.970305093821.4589C-100000@itsrm1.mow.sni.de \
--to=borsenkow.msk@sni.de \
--cc=luomat@peak.org \
--cc=zsh-users@math.gatech.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).