Xref: utzoo comp.unix.xenix.sco:2055 comp.unix.questions:29916 comp.unix.wizards:24604
Newsgroups: comp.unix.xenix.sco,comp.unix.questions,comp.unix.wizards
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!van-bc!cynic!curt
From: curt@cynic.wimsey.bc.ca (Curt J. Sampson)
Subject: ISTRIP in /etc/gettydefs
Organization: Mad Artists' Technological Hangout
Date: Sat, 30 Mar 1991 01:53:59 GMT
Message-ID: <1991Mar30.015359.28174@cynic.wimsey.bc.ca>
Followup-To: comp.unix.xenix.sco
Summary: Why doesn't ISTRIP work when turned on in the initial-flags?
Keywords: getty login termio parity
Sender: curt@cynic.wimsey.bc.ca (Curt J. Sampson)

I've got a friend who's trying to log in from a terminal that supports
either mark, even or odd parity (but not none, unfortunately).  The
easiest thing to do to support all parity settings seemed to be to
have getty set up with CS8 and ISTRIP so that it would essentially
ignore the parity bit.  This works fine for the final-flags section
(the settings that it uses just before executing login).
Unfortunately, getty won't turn on ISTRIP, even if asked, for its
initial-flag settings.

This means that the person logging in can never log in successfully
the first time.  They have to type something that will cause getty to
invoke login, hit return at the Password: prompt, and then log in
normally.  This is obviously only a minor inconvenience, of course.

Is this a bug, or a feature?  Is there a fix for it?  Am I just doing
something wrong?

cjs
-- 
                        | "It is actually a feature of UUCP that the map of
curt@cynic.uucp         | all systems in the network is not known anywhere."
curt@cynic.wimsey.bc.ca |    --Berkeley Mail Reference Manual (Kurt Schoens)