From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Russian keyboard
Date: Mon, 23 Sep 2002 10:00:42 +0200 [thread overview]
Message-ID: <9af3d93e90ba8c45b5dc8f1f852ee06c@plan9.escet.urjc.es> (raw)
[-- Attachment #1: Type: text/plain, Size: 604 bytes --]
: sent to /dev/kbmap)? What are the disadvantages of such a scheme
: compared to compiled-in maps?
A compiled map can be activated even before you get the
connection to the file system. That's useful, since usually
people have to type weird characters to choose their boot file
system (if other than default).
Here we compile the us and the spanish maps, and both students
(spanish map) and me (us map) can type using the preferred map
at the root / user / secstore passwd prompts.
I'll merge your map into the kbmap tar after generating a .c
file from your map file.
thanks a lot
[-- Attachment #2: Type: message/rfc822, Size: 6204 bytes --]
[-- Attachment #2.1.1: Type: TEXT/PLAIN, Size: 938 bytes --]
Hello,
with some pushing from Andrey Kuchar (thanks!), I have made
a Russian keyboard map for use with nemo's keyboard drivers.
To use it, you need to compile the kernel with /dev/kbmap
support -- diffs to nemo's /sys/src/9/pcdisk attached. Upon
startup (in /bin/termrc, preferably), you need to do
bind -a '#О©╫' /dev
cat /lib/kbmap/kbd_ru.map > /dev/kbmap
It replaces the Bulgarian keymap (I doubt anyone would want to
use both).
Now the question:
I don't like the idea of having lots of kbmaps compiled into
the kernel (That's why I didn't make kbmap_ru.c). I'd probably
prefer several maps, initialized to kbmap_default, and
controlled via /dev/kbmap. Should I make such changes? Should
maps appear dynamically (for example, a map appears
when a "reset n" or "keymap n" message with a new n is
sent to /dev/kbmap)? What are the disadvantages of such a scheme
compared to compiled-in maps?
Goga
[-- Attachment #2.1.2: Type: TEXT/PLAIN, Size: 360 bytes --]
src/sys/src/9/pc/pcdisk:35 a /sys/src/9/pc/pcdisk:36,37
> kbmap
>
src/sys/src/9/pc/pcdisk:49 d /sys/src/9/pc/pcdisk:50
< etherwavelan wavelan devi82365 cis pci
src/sys/src/9/pc/pcdisk:93,99 d /sys/src/9/pc/pcdisk:93
< kbd_es
< kbd_fr
< kbd_uk
< kbd_jp
< # this should be in the dev section
< # as a "kbmap" entry, and not here.
< devkbmap
[-- Attachment #2.1.3.1: Type: text/plain, Size: 430 bytes --]
The following attachment had content that we can't
prove to be harmless. To avoid possible automatic
execution, we changed the content headers.
The original header was:
Content-Type: TEXT/PLAIN; charset=koi8-r; name="kbd_ru.map"
Content-Transfer-Encoding: BASE64
Content-ID: <Pine.LNX.4.44L.0209221445231.2471@corneja.rubinstein.mccme.ru>
Content-Description:
Content-Disposition: attachment; filename="kbd_ru.map"
[-- Attachment #2.1.3.2: kbd_ru.map.suspect --]
[-- Type: application/octet-stream, Size: 1076 bytes --]
reset 2
keymap 2
key 0x01 0x1b 0x1b
key 0x02 '1' '!'
key 0x03 '2' '"'
key 0x04 '3' '#'
key 0x05 '4' '$'
key 0x06 '5' ':'
key 0x07 '6' ','
key 0x08 '7' '.'
key 0x09 '8' ';'
key 0x0a '9' '('
key 0x0b '0' ')'
key 0x0c '-' '_'
key 0x0d '=' '+'
key 0x0e 0x08 0x08
key 0x0f 0x09 0x09
key 0x10 'й' 'Й'
key 0x11 'ц' 'Ц'
key 0x12 'у' 'У'
key 0x13 'к' 'К'
key 0x14 'е' 'Е'
key 0x15 'н' 'Н'
key 0x16 'г' 'Г'
key 0x17 'ш' 'Ш'
key 0x18 'щ' 'Щ'
key 0x19 'з' 'З'
key 0x1a 'х' 'Х'
key 0x1b 'ъ' 'Ъ'
key 0x1c 0x0a 0x0a
key 0x1e 'ф' 'Ф'
key 0x1f 'ы' 'Ы'
key 0x20 'в' 'В'
key 0x21 'а' 'А'
key 0x22 'п' 'П'
key 0x23 'р' 'Р'
key 0x24 'о' 'О'
key 0x25 'л' 'Л'
key 0x26 'д' 'Д'
key 0x27 'ж' 'Ж'
key 0x28 'э' 'Э'
key 0x29 'ё' 'Ё'
key 0x2b 0x5c '|'
key 0x2c 'я' 'Я'
key 0x2d 'ч' 'Ч'
key 0x2e 'с' 'С'
key 0x2f 'м' 'М'
key 0x30 'и' 'И'
key 0x31 'т' 'Т'
key 0x32 'ь' 'Ь'
key 0x33 'б' 'Б'
key 0x34 'ю' 'Ю'
key 0x35 '/' '?'
next reply other threads:[~2002-09-23 8:00 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-23 8:00 Fco.J.Ballesteros [this message]
2002-09-23 19:09 ` George Bronnikov
2002-09-23 22:11 ` Dan Cross
-- strict thread matches above, loose matches on Subject: below --
2002-10-01 7:09 Andrew Simmons
2002-09-30 12:12 Skip Tavakkolian
2002-09-30 15:58 ` LacOniC
2002-09-30 4:21 Russ Cox
2002-09-30 4:25 ` Jim Choate
2002-09-26 7:23 Fco.J.Ballesteros
2002-09-26 20:56 ` George Bronnikov
2002-09-26 21:30 ` Jack Johnson
2002-09-26 22:01 ` andrey mirtchovski
2002-09-27 11:19 ` Boyd Roberts
2002-09-30 2:20 ` Jim Choate
2002-09-30 2:35 ` Dan Cross
2002-09-30 2:58 ` Jim Choate
2002-09-30 3:14 ` Dan Cross
2002-09-30 4:15 ` Jim Choate
2002-09-30 4:33 ` William Josephson
2002-09-30 4:34 ` Jim Choate
2002-09-30 4:45 ` William Josephson
2002-09-30 5:41 ` Jim Choate
2002-09-30 6:23 ` Tomas
2002-09-30 12:05 ` Jim Choate
2002-09-24 13:46 Fco.J.Ballesteros
2002-09-25 20:28 ` George Bronnikov
2002-09-24 13:45 Fco.J.Ballesteros
2002-09-24 2:42 anothy
2002-09-24 0:46 Andrey S. Kukhar
2002-09-23 20:41 Andrey S. Kukhar
2002-09-23 13:40 Fco.J.Ballesteros
2002-09-23 8:04 Fco.J.Ballesteros
2002-09-22 10:45 George Bronnikov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9af3d93e90ba8c45b5dc8f1f852ee06c@plan9.escet.urjc.es \
--to=nemo@plan9.escet.urjc.es \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).