Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!husc6!cmcl2!phri!marob!manes
From: manes@marob.MASA.COM (Steve Manes)
Newsgroups: comp.unix.xenix
Subject: Re: Xenix 2.3 getty
Message-ID: <420@marob.MASA.COM>
Date: 17 Dec 88 14:00:33 GMT
References: <1317@cps3xx.UUCP>
Organization: ESCC  New York City
Lines: 21

From article <1317@cps3xx.UUCP>, by usenet@cps3xx.UUCP (Usenet file owner):
> No real solution to this other than having the user type ctrl-j
> after their account name.  After that all preceeds well.  Anyone
> with a better solution?  I've tried playing with the gettydefs
> file without any sucess.

I notified SCO of the problem and they've placed the bug report on
escalated-something.   Getty is ignoring all initial flag settings
except SANE, RTSFLOW and CTSFLOW and apparently setting the terminal to
8/N + ISTRIP internally, which is exactly what I want.  However it's not
mapping CR to LF, as you noted.  With all the nice stuff in the new
getty, especially its reading Devices/Dialers for modem reset codes,
it's strange that SCO didn't also enable /etc/issue.  For that matter,
it would also be nice if getty could be updated to the
baud-querying/sensing technology of your average 1982 DOS BBS.  A CR at
some baud rates doesn't generate the parity error getty needs to cycle
gettydefs and a modem BREAK is arcana to most non-Unix folks.
-- 
Steve Manes		Roxy Recorders, Inc.		Magpie-HQ BBS
UUCP : {rutgers|cmcl2}!hombre!magpie!manes		(212)420-0527
Smail: manes@MASA.COM