Re: Stty bug?

[Alan Curry]

Tom Lake writes:
> 
> >> I believe -iexten may be the problem. In your tty1 test, was iexten 
> >> enabled?
> >> Maybe a getty bug, it should be turning on iexten if it turns on iuclc.
> > 
> > I was able to recreate the original problem.  Reading Alan's response
> > here I was surprised to see that adding iexten to iuclc did enable the
> > desired behavior.  This would not have been required on traditional
> > systems and its combination here isn't obvious to me.  There doesn't
> > seem to be very much documentation available about iexten.  I am
> > curious how you deduced that adding it would produce the desired
> > behavior?
> 
> Sorry to report that it didn't work for me.  I tried both iexten and -iexten
> for good measure.  It seems like whenever getty is respawned, it changes 
> /dev/ttyS0 to whatever it wants no matter what stty does.  I still couldn't 

To do a successful test without patching getty, you'd have to do the stty
from another terminal after entering the username but before the password.
Or make a test account with a password that doesn't have any letters in it.

Either way, even with the buggy getty, you should at least get an
all-uppercase "PASSWORD:" prompt after typing an uppercase username. Does the
password prompt look OK? (What would it look like if the computer was sending
it lowercase ASCII codes? garbage I assume, so a readable password prompt is
a sign things are working up to that point.)

By the way, suggested getty diff:

--- agetty.c.orig       2010-02-12 18:12:46.000000000 -0500
+++ agetty.c    2010-02-12 18:13:38.000000000 -0500
@@ -1138,7 +1138,7 @@
     /* General terminal-independent stuff. */
 
     tp->c_iflag |= IXON | IXOFF;               /* 2-way flow control */
-    tp->c_lflag |= ICANON | ISIG | ECHO | ECHOE | ECHOK| ECHOKE;
+    tp->c_lflag |= ICANON | ISIG | ECHO | ECHOE | ECHOK| ECHOKE | IEXTEN;
       /* no longer| ECHOCTL | ECHOPRT*/
     tp->c_oflag |= OPOST;
     /* tp->c_cflag = 0; */

-- 
Alan Curry