Subject: misc/2502: ttys don't have crt erase/kill capabilities on login
To: None <gnats-bugs@NetBSD.ORG>
From: Perry E. Metzger <email@example.com>
Date: 06/01/1996 19:00:36
>Synopsis: ttys don't have crt erase/kill capabilities on login
>Responsible: misc-bug-people (Misc Bug People)
>Arrival-Date: Sat Jun 1 19:20:03 1996
>Originator: Perry E. Metzger
Perry Metzger firstname.lastname@example.org
System: NetBSD jekyll.piermont.com 1.2_ALPHA NetBSD 1.2_ALPHA (JEKYLL) #46: Sat Jun 1 14:07:34 EDT 1996 email@example.com:/usr/src/sys/arch/i386/compile/JEKYLL i386
Login terminals get initialized pretty badly. When you start using a
fresh terminal (like a login terminal) it doesn't have enough
flags needed to set crt-style behavior, even on the average
This may be because the default gettytab is deficient in the
flags that are set in it, or it may be that the tty driver
doesn't pick a particularly friendly set of defaults.
It didn't used to be the case that you had to do an stty sane crt
-- I don't recall 1.0 featuring this, for example.
Log in using most shells. Hit delete. Notice the echoed
^?. Hit ^U. Notice the echoed ^U.
The obvious workaround for a user is to add an stty sane crt
into every .login he has on earth, but that feels poor.
It appears that entries like the Pc entry (and possibly
others) in gettytab can have flags like :ce: and :ck:
added, though whether this is a complete fix (other flags or
better flags should perhaps be used?) or is the best fix
(shouldn't the ttys have better defaults when they are reset?)
is unknown to the author. Certainly adding these flags
improved my own quality of life.
The problem didn't used to happen way back when -- I haven't
checked the source tree to see if this was because of changes
in the tty driver or changes in the gettytab file over time.