From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] getting rid of kernel kbd maps
Date: Wed, 12 Nov 2003 12:17:24 +0100 [thread overview]
Message-ID: <6a6622ae150975f845c23e4cbe38ce23@plan9.escet.urjc.es> (raw)
In-Reply-To: <28601514.0311111235.5ffb44c@posting.google.com>
[-- Attachment #1: Type: text/plain, Size: 305 bytes --]
??
Don't understand.
Currently, the alternate driver services maps.
I'd like to get rid of it. THere's also a user level
(usb) driver that could be modified to operate
on cons(3) to translate keys (i.e. to implement
the keymaps without putting the burden in the
kernel). That was the proposal.
[-- Attachment #2: Type: message/rfc822, Size: 2317 bytes --]
From: Ramon <ramon_gnews@terra.es>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] getting rid of kernel kbd maps
Date: Wed, 12 Nov 2003 09:38:33 GMT
Message-ID: <28601514.0311111235.5ffb44c@posting.google.com>
I oppose that usage of keys. The user can change the keyboard mapping
using an application. For password prompt, I think that this part of
the boot process should be stored in a shell script, perhaps stored in
a virtual disk inside the kernel image. That is IHMO needed anyway, so
that the startup process can be customized without recompiling the
kernel.
Ramon
next prev parent reply other threads:[~2003-11-12 11:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-10 17:09 Fco.J.Ballesteros
2003-11-10 17:26 ` mirtchov
2003-11-10 17:33 ` Fco.J.Ballesteros
2003-11-12 9:38 ` Ramon
2003-11-12 11:17 ` Fco.J.Ballesteros [this message]
2003-11-10 18:36 ` Dan Cross
2003-11-10 18:42 ` 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=6a6622ae150975f845c23e4cbe38ce23@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).