phil@amdcad.UUCP (Phil Ngai) (12/03/85)
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.
If we can have a virtual terminal, why not a virtual stty....
Pardon me if rlogin is supposed to do this and it's just my vendor
who has slipped up.
--
There's nothing I hate more than sorting socks.
Phil Ngai +1 408 749-5720
UUCP: {ucbvax,decwrl,ihnp4,allegra}!amdcad!phil
ARPA: amdcad!phil@decwrl.dec.combobr@zeus.UUCP (Robert Reed) (12/04/85)
> 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