From: Erik Quanstrom <quanstro@quanstro.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Raspberry Pi: keyboard layout
Date: Sun, 2 Dec 2012 19:57:41 -0500 [thread overview]
Message-ID: <tjakq2eu90gjhxram2e9yc7n.1354496219124@email.android.com> (raw)
I'd guess the kernel doesn't have that device built in.
- erik
Murray Colpman <muzerakascooby@gmail.com> wrote:
>Hi all,
>
>I'm an absolute beginner to Plan 9, I just installed it on my Raspberry
>Pi for fun to have a see what it's all about. I understand this being a
>very new build there are likely to be some issues, so do know that I'm
>not holding my not-so-smooth experience against Plan 9 ;)
>
>After a lot of wrangling with getting it compatible with my custom boot
>menu (actually a very hacky Linux binary that shoves the necessary
>config files into the Raspberry Pi boot partition and reboots, each OS
>having to manually put the boot menu config files back in place on
>boot), helped by some very nice people in #plan9 on Freenode, I now move
>onto the other problems.
>
>The biggest one for me, being a Dvorak user, is that I cannot get the
>keyboard layouts working. I'm starting to form a vague idea in my head
>about how Plan 9 is working, but I probably have a lot of things wrong,
>so do bear with me.
>
>When I run the kbmap program, attempting to set a map flashes up an
>error about not being able to find /dev/kbmap. Looking at the manpages,
>it seems that /dev/kbmap is supposed to be brought in with bind -a
>'#kappa' /dev (with kappa obviously replaced with the actual kappa
>letter). I did snarf the kappa from the manpage, and I also tried typing
>it on the keyboard in various ways (compose, *, k for instance), so I
>don't think that the issue is that I'm unable to type kappa correctly.
>Anyway, when I run this bind command, I get "bind: #kappa: unknown
>device in # filename" (again, kappa replaced with the actual kappa).
>
>
>Any ideas?
>
>
>Thanks a lot,
>Murray Colpman.
>
>
next reply other threads:[~2012-12-03 0:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-03 0:57 Erik Quanstrom [this message]
2012-12-03 1:05 ` Murray Colpman
-- strict thread matches above, loose matches on Subject: below --
2012-12-03 0:45 Murray Colpman
2012-12-03 1:08 ` Bakul Shah
2012-12-03 1:33 ` Murray Colpman
2012-12-03 2:10 ` Christopher Wilson
2012-12-03 9:42 ` Richard Miller
2012-12-03 16:44 ` Murray Colpman
2012-12-03 17:00 ` Richard Miller
2012-12-03 19:38 ` Chris Wilson
2012-12-04 1:52 ` Bakul Shah
2012-12-04 2:41 ` erik quanstrom
2012-12-03 16:23 ` Christian Neukirchen
2012-12-03 16:48 ` Richard Miller
2012-12-04 14:10 ` Christian Neukirchen
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=tjakq2eu90gjhxram2e9yc7n.1354496219124@email.android.com \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).