> Has anyone yet figured out why, after running for while, the Xmacbsd 
> suddenly stops recognizing the keystroke 'a'?  Other keystrokes work just 
> fine (including 'A'), and the 'a' works great after killing X.

Are you using a window manager other than twm supplied?  MacBSD X
server has a bug; it uses Key Codes 0 thru 7 which aren't supposed to
be used.  It passes the raw scan code to X apps as the key code, and
guess what, the scan code of the 'a' key is 0.  Some X apps (including
wm's) are apparently more sensitive to this key code 0 than others.  I
suggested a fix to Allen for this bug, and he says it's fixed in his
source tree.  Wait for the next release!

kenn
--
Ken Nakata <kenn@remus.rutgers.edu> | "ftp://remus.rutgers.edu/pub/NetBSD" -
 Rutgers - The State University of  | yet another unofficial NetBSD/mac68k
            New Jersey              | anon-FTP area.  For more NetBSD info,
     New Brunswick, New Jersey      | visit "http://www.NetBSD.ORG/".