9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Christopher Wilson <christopher.j.wilson@gmail.com>
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 20:10:32 -0600	[thread overview]
Message-ID: <CAOxF3fEkOsmu3yjRidD2wQ7TbjK-RYJwqjk-FSvD_1AKgg6_6w@mail.gmail.com> (raw)
In-Reply-To: <50BC014F.7090206@gmail.com>

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

I seem to remember that there is already a dvorak key map somewhere in Plan
9. I was able to just use it.
On Dec 2, 2012 7:34 PM, "Murray Colpman" <muzerakascooby@gmail.com> wrote:

> On 03/12/12 01:08, Bakul Shah wrote:
> > On Mon, 03 Dec 2012 00:45:29 GMT Murray Colpman <
> muzerakascooby@gmail.com>  wrote:
> >> 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).
> >
> > You need to compile the driver in.  Add
> >       kbmap
> > to the dev section in config file /sys/src/9/bcm/pi.  mk and
> > then copy 9pi to the dos partition.
> >
> >       dossrv -f /dev/sdM0/dos
> >       mount -c /sv/dos /n/dos
> >       cp /sys/src/9/bcm/9pi /n/dos/9pi
> >       fshalt
> >
> Thank you very much for the instructions!
>
> Just tried it, kbmap now works perfectly, and I have now set the
> keyboard map in my lib/profile. It all works :D - now I just have to
> hack together a UK Dvorak - the map files look easy enough to fiddle
> with. I'll do this tomorrow as I should really be sleeping now, though.
>
> Thanks a lot!
> Murray Colpman.
>
>

[-- Attachment #2: Type: text/html, Size: 2161 bytes --]

  reply	other threads:[~2012-12-03  2:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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
2012-12-03  0:57 Erik Quanstrom
2012-12-03  1:05 ` Murray Colpman

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=CAOxF3fEkOsmu3yjRidD2wQ7TbjK-RYJwqjk-FSvD_1AKgg6_6w@mail.gmail.com \
    --to=christopher.j.wilson@gmail.com \
    --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).