Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 (Tek) 9/28/84 based on 9/17/84; site zeus.UUCP
Path: utzoo!watmath!clyde!cbosgd!ihnp4!houxm!vax135!cornell!uw-beaver!tektronix!teklds!zeus!bobr
From: bobr@zeus.UUCP (Robert Reed)
Newsgroups: net.unix-wizards
Subject: Re: does rlogin preserve stty settings between BSD and System V?
Message-ID: <225@zeus.UUCP>
Date: Wed, 4-Dec-85 15:31:04 EST
Article-I.D.: zeus.225
Posted: Wed Dec  4 15:31:04 1985
Date-Received: Sat, 7-Dec-85 03:28:41 EST
References: <7070@amdcad.UUCP>
Organization: Tektronix, Beaverton OR
Lines: 23

> Is it reasonable to expect rlogin to pass your stty settings along to
> a remote host when that host runs a different version of Unix? I am
> thinking in particular of rlogin between BSD and System V. If I have
> stty crt on a local BSD machine, I would like stty echoe on the remote
> System V machine, but it seems perhaps too much to expect.
> 
>  Phil Ngai +1 408 749-5720
>  UUCP: {ucbvax,decwrl,ihnp4,allegra}!amdcad!phil
>  ARPA: amdcad!phil@decwrl.dec.com

rlogin should have to pass your stty settings along.  It should only have to
do an stty raw on the local host and pass some environment stuff like $TERM
on to the remote host.  Given that the local host is a nearly transparent
filter (excepting ~ escapes), the login process on the remote host should
handle any special stty needs, etc.

We had a problem locally with rlogin NEARLY setting the local terminal
driver to raw--except for ^S/^Q flagging.  The result was that rlogged-in
users who attempted editing with Emacs found that the typical bindings for
these keys were nonfunctional.  The fix was to make the local driver truly
transparent.
-- 
Robert Reed, CAE Systems Division, tektronix!teklds!bobr