On Tue, Apr 25, 2006 at 09:19:59PM +0000, Christos Zoulas wrote:
> In article <20060425205316.GA11023@yuba.kcn.ne.jp>,
> Henry Nelson  <netb@yuba.kcn.ne.jp> wrote:
> >I *thought* I had a serial console working fine on i386, but at the
> >login prompt, "@" acts like ^u and "#" acts like Backspace.  Once
> >logged in, the keyboard acts normally -- it's only at the login
> >prompt and password input.
> >
> >Ideas?  This one has me totally stumped.
> 
> man gettytab?

Sorry, still not sure what to do.

Should I edit "/etc/gettytab" and change
        default:\
                :ce:ck:np:im=\r\n%s/%m (%h) (%t)\r\n\r\n:
to
        default:\
                :er='^?':kl='^u':ce:ck:np:im=\r\n%s/%m (%h) (%t)\r\n\r\n:

I don't recall ever having such a problem on sparc (IPC, Classic, SS5).  Is
there something inherently different between sparc and i386 in the way getty
works?  (IIRC, I have never used wscons with sparc, and am a bit new to it,
if that is the source of my problems.  See 2nd question below.)

After logging in, wscons takes over, so I no longer have a problem; is that
right?

In "/etc/tty" I have:
        console "/usr/libexec/getty std.38400"  vt220   on secure
        ttyE0   "/usr/libexec/getty Pc"         vt220   on secure
, and in "/etc/wscons.conf" I have uncommented the "screen 0" line.
Is this my mistake?  Should I only have one or the other of "console"
or "ttyE0" turned on, not both at the same time?

TIA

-- 
henry nelson
  WWW_HOME=http://yuba.kcn.ne.jp/~home/