Xnest and pc104 kb

[Nemo - earth native]

On Mon, Sep 16, 2002 at 09:42:37AM +1000, Doug.Palmer at csiro.au did utter:

> Have a look in /usr/X11R6/lib/X11/xkb/keymap/xfree86 (possibly varied

yup, it's there (though sensibly symlinked to within /etc by debian
policy ;)

> somewhat depending on distribution). This file is what maps the keymap
> statement onto the sets of symbols/keyboard layouts/etc that XKB uses. My
> file has an entry something like 
> 
> default xkb_keymap "us" {
>     xkb_keycodes    { include "xfree86"     };
>     xkb_types       { include "default"     };
>     xkb_compatibility   { include "default"     };
>     xkb_symbols     { include "us(pc105)"       };
>     xkb_geometry    { include "pc"          };
> };

looks the same to mine - the default seems to be us with an include on
pc105... 

When I try and use the -xkbmap option directly, I get, for example:

$ Xnest -xkbmap xfree86  :2
Error opening keymap file xfree86, reverting to defaults

Trying with an explicit keymap...

$ Xnest -xkbmap xfree86\(us_microsoft\) :2
Error opening keymap file xfree86(us_microsoft), reverting to defaults


So, wah. It finds the file, but has an error opening it?!

...and yet regardless, the default - as indicated in that xfree86 file,
is as you pasted above.. and should give me pc105... 

yet I still get:
_XKB_RULES_NAMES(STRING) = "xfree86", "pc101", "us", "", ""

(I get a pc104 on the "real" Xserver, as defined in my XF86Config-4
file...

...the -xkbdb seems to happy to accept anything I give it, and nothing I
give it changes anything. 


*grah*

I guess I could solve the essential right-now problem with xmodmap - but
that always seems to me to be kinda hackish. I'd rather convince Xnest
to load the right keymap from the start...

wah. Can anyone else get Xnest to see a pc104 or pc105 straight off the
bat?

.../Nemo