On 3/29/06, jpdrawneek <[EMAIL PROTECTED]> wrote:
> ok, i have changed the keymap file in /usr/openwin/etc/keymap/
>
> but it has not made a difference, any ideas?
Did you log out from the Sun Ray with the cheap keyboard after
you'd edited the keytable.map file?
What does 'grep \^6 /usr/openwin/etc/keytables/keytable.map'
show?
What make and model of keyboard is this? It's possible that
somebody has already figured out what it needs.
> This is on sparc, and the keyboard is probably the cheapest nasties you
> can find.
Maybe it's so nasty that it reports some totally bogus layout code.
I'd proceed by plugging the cheap keyboard into a Sun Ray that
already has a Sun keyboard plugged in. Then, using only the
Sun keyboard:
- log in
- open a terminal window
- in that window, 'su' to root
- start a 'truss' of the Xsun process for this session. Make sure
that you direct the output of the 'truss' into a file by using the
'-o filename' option, otherwise you'll deadlock the session. If
this makes you nervous (it should) then consider running the
'truss' from someplace outside this X session. Find the Xsun
process by looking for an Xsun process whose display argument
matches your session's $DISPLAY environment variable.
After the 'truss' is running, type a few characters on the cheap
keyboard, then control-C the 'truss' process. Then look at the 'open'
calls in the 'truss' output file to see which keytable Xsun tried to
load when it saw keystrokes from the cheap keyboard. That should
let you figure out what layout code the keyvboard reported, and
therefore which line in the keytable.map file you need to edit to
get it to use the UK6.kt key table.
OttoM.
__
ottomeister
Disclaimer: These are my opinions. I do not speak for my employer.
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
