Reginald Beardsley wrote:
Having established that the stty behavior is a red herring produced by
/bin/tcsh here is a precis of the situation (pwd is /etc):
oi%rhb {180} /app/bin/rcsdiff remote ttydefs
===================================================================
RCS file: RCS/remote,v
retrieving revision 1.1
diff -r1.1 remote
5a6
u0::dv=/dev/cua/0:br#9600:el=^C^S^Q^U^D:ie=%$:oe=^D:
===================================================================
RCS file: RCS/ttydefs,v
retrieving revision 1.1
diff -r1.1 ttydefs
63a64
msp430:9600 -parenb cs8 -cstopb ixon opost olcuc onlcr:9600 hupcl sane::msp430
oi%rhb {181} pmadm -l
PMTAG PMTYPE SVCTAG FLGS ID <PMSPECIFIC>
zsmon ttymon tty0 u root /dev/term/0 b -
/usr/bin/login - msp430 ldterm,ttcompat login: - - - -S n #MSP430
oi%rhb {182} /bin/sh
rhb@openindiana:/etc$ tip u0
connected
ok.
ok.
ok.
~
[EOT]
rhb@openindiana:/etc$ stty -a
You're running stty on your terminal, not on /dev/term/b.
Try running "stty -a < /dev/term/b" whilst you have the tip running on it.
(or I'm misunderstanding what you're trying to do.)
--
Andrew
_______________________________________________
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss
