Tiny Core Linux
Tiny Core Base => TCB Talk => Topic started by: bmarkus on September 12, 2009, 07:31:27 AM
-
/etc/sysconfig/keymap specifies the requested keymap. Use it to modify keyboard layout in /etc/X11/xorg.conf if file and keyboard section exist before X started; same can be done for Xvesa by the X startup script. In such case kmap boot option would work automatically for X environment.
-
Would require bigish translation tables. Even the basename of the keymaps is not consistent across all keymaps in X and console.
Xvesa? Could you elaborate? Xvesa can't use X keymaps, and uses console keymaps automatically if loaded by the kmap boot option.
-
Would require bigish translation tables. Even the basename of the keymaps is not consistent across all keymaps in X and console.
I don't think that any translation table is needed, just copy the string from /etc/sysconfig/keymap and leave it up to the user to enter proper value. If X is used, it will work for terminals also started, only ordinary terminal will not see the config, but that's it.
Xvesa? Could you elaborate? Xvesa can't use X keymaps, and uses console keymaps automatically if loaded by the kmap boot option.
Well, I do not know Xvesa, expected to have a similar option in the config. It looks like I was wrong, sorry.
-
I don't think that any translation table is needed, just copy the string from /etc/sysconfig/keymap and leave it up to the user to enter proper value. If X is used, it will work for terminals also started, only ordinary terminal will not see the config, but that's it.
Ah, so you mean to try to use the kmap option for both console and X, ignoring if it doesn't work for one?
It would work, but I don't see it necessary in the core, because Xorg itself is an extension. A remaster requiring this can easily script it in bootlocal.sh.