9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] keymaps question. would this be acceptable for you all?
Date: Wed, 12 Nov 2003 12:34:36 +0100	[thread overview]
Message-ID: <d1d04c00d38f6193dc4669c63ccb7f03@plan9.escet.urjc.es> (raw)
In-Reply-To: <3fb20a7e$0$13405$79c14f64@nan-newsreader-03.noos.net>

[-- Attachment #1: Type: text/plain, Size: 700 bytes --]

The problem is that you need your own keymap setup at
boot(8) time, or you'll have problems typing your password
(unless your password is a naive one that stays the same
no matter the keyboard used). Remember, there's no fs
where to get the keymap from, but you still need that map.

In fact, what I'm proposing is to `move' kbmap (and a couples of
fixed tables) out of the kernel, into the user-level keyboard
driver that can be started by boot. The tables used by such
driver are similar to those of /dev/kmap: go from this rune to this
other rune.

As an extra benefit, we could get rid of the kernel code for devkbmap,
static keymaps, and compose.

Is there anything I'm missing?

[-- Attachment #2: Type: message/rfc822, Size: 2113 bytes --]

From: Boyd Roberts <boyd@insultant.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] keymaps question. would this be acceptable for you all?
Date: Wed, 12 Nov 2003 11:13:57 GMT
Message-ID: <3fb20a7e$0$13405$79c14f64@nan-newsreader-03.noos.net>

what was ever wrong with forthsyth's /dev/kbmap stuff?

(well i can think of one or things, but there's not much he he can do about
it)

it's the one thing lunix gets right: very early on it asks you
where you are, what you're typing on and who's the leader
of the opposition ...

  reply	other threads:[~2003-11-12 11:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-12  9:12 Fco.J.Ballesteros
2003-11-12 11:13 ` Boyd Roberts
2003-11-12 11:34   ` Fco.J.Ballesteros [this message]
2003-11-12 11:39     ` boyd, rounin
2003-11-12 11:45       ` Fco.J.Ballesteros
2003-11-12 12:02         ` boyd, rounin
2003-11-12 13:39           ` Fco.J.Ballesteros

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=d1d04c00d38f6193dc4669c63ccb7f03@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).