Return to BSD News archive
Newsgroups: comp.os.386bsd.questions
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!torn!csd.unb.ca!b6ps
From: b6ps@jupiter.sun.csd.unb.ca (Peter Howlett)
Subject: Re: [netbsd 0.9] terminal on com ports
Message-ID: <1993Oct18.153229.26239@jupiter.sun.csd.unb.ca>
Organization: University of New Brunswick
References: <D> <1993Oct13.121947.19474@jupiter.sun.csd.unb.ca> <29he6r$t1j@homer.cs.mcgill.ca>
Date: Mon, 18 Oct 1993 15:32:29 GMT
Lines: 27
In article <29he6r$t1j@homer.cs.mcgill.ca> storm@cs.mcgill.ca (Marc WANDSCHNEIDER) writes:
>In article <1993Oct13.121947.19474@jupiter.sun.csd.unb.ca>,
>Peter Howlett <b6ps@elara.sun.csd.unb.ca> wrote:
>>
>>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?
It worked for me. I did however, try setting my vt52 terminal to 7 data
bits and even parity before resorting to resetting my serial port
every time I log in, but that did'nt work. It was very strange. At
any rate, my terminal (a vt52/ansi) after years of loyal service
has finially died (bad flyback), so I find myself without a backup
when something happens to my console.
Good Luck,
-------------------------------------------------------------------
From: Peter Howlett University of New Brunswick
Inet: b6ps@jupiter.csd.unb.ca