Return to BSD News archive
Newsgroups: comp.os.386bsd.bugs
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!europa.eng.gtefsd.com!uunet!psinntp!newstand.syr.edu!rodan.syr.edu!dhhoveme
From: dhhoveme@rodan.syr.edu (David H. Hovemeyer)
Subject: NetBSD 0.9: stty problems on com1
Message-ID: <1993Sep6.204821.28957@newstand.syr.edu>
Organization: Syracuse University, Syracuse, NY
Date: Mon, 6 Sep 93 20:48:21 EDT
Lines: 34
I am still having problems with a VT102 terminal connected to com1.
What seems to be happening is that the stty settings are hosed by
programs that do terminal I/O (elvis, more). Immediately after
logging in, the stty settings are as follows:
speed 9600 baud;
lflags: echoe echok echoke echoctl
iflags: istrip
oflags: -oxtabs
cflags: cs7 parenb
The terminal, configured for 9600 baud and 7E parity, seems happy
with this arrangement. After more (or elvis) is run, the settings
(as reported by a stty -f /dev/com1) become:
speed 9600 baud;
lflags: echoe echok echoke echoctl
iflags: istrip
oflags: -oxtabs
cflags: cs7 -parenb
^^^^^^^
Aparently, when more is run, parity generation/detection is turned
off. My questions are:
what is causing this?
how can I fix it?
If you have some ideas or suggestions, I would be glad to hear them.
Dave
--
dhhoveme@rodan.acs.syr.edu