Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!usc!cs.utexas.edu!uwm.edu!rpi!utcsri!newsflash.concordia.ca!sifon!homer.cs.mcgill.ca!storm
From: storm@cs.mcgill.ca (Marc WANDSCHNEIDER)
Newsgroups: comp.os.386bsd.questions
Subject: Re: [netbsd 0.9] terminal on com ports
Date: 13 Oct 1993 17:34:19 GMT
Organization: SOCS, McGill University, Montreal, Canada
Lines: 30
Message-ID: <29he6r$t1j@homer.cs.mcgill.ca>
References: <2956kr$bm5@homer.cs.mcgill.ca> <D> <1993Oct13.121947.19474@jupiter.sun.csd.unb.ca>
NNTP-Posting-Host: mnementh.cs.mcgill.ca
In article <1993Oct13.121947.19474@jupiter.sun.csd.unb.ca>,
Peter Howlett <b6ps@elara.sun.csd.unb.ca> wrote:
>
>Using the "on secure" options in ttys has always worked for me. Cant help
>here.
This is odd-- A couple of other people I have talked to have also
confirmed having the same problem as I do...
>
>This was a question of mine earlier this month, which some nice people told
>me was because getty resets the line settings on the com port to cs7 and
>parenb. (7 data bits and even parity.) This seems to happen no matter what
>is in the gettytab file. All I did was put an stty in my .login file and
>everything is cool now.
This is bizarre as hell then, because my terminal is an old
3151 which is SET to e71 right now already....
Perhaps an 'stty cs7 parenb' in my .login will help fix this?
Thoughts?
Marc 'em.
--
----------------------------------------------------------------------------
Marc Wandschneider Seattle, WA
Free/Net BSD---Real UN*X, Really Free