From: Robert Hibberdine <bob.hibberdine@ntlworld.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] setting up a differnet keyboard
Date: Thu, 17 Jul 2008 22:12:39 +0100 [thread overview]
Message-ID: <487FB5C7.5030908@ntlworld.com> (raw)
In-Reply-To: <deabf8040afa719a1df3718a27bc5d9c@quanstro.net>
Many thanks for this recipe.
For the moment, though, I am going to stick with my
cp /sys/lib/kbmap/uk /dev/kbmap in my profile
Unless there is a good reason why I shouldn't....?
Bob
erik quanstrom wrote:
>> In which case, this doesn't seem to be a very practical mechanism.
>> Wouldn't it be beter to attach to the server and then do the kbmap()
>> stuff ??
>>
>
> that's a good chicken-and-egg question. at the stage of boot
> where kbmap is run, factotum has not been run and there is no
> fileserver. the advantage to doing the mapping here is that
> passwords can be entered normally. the disadvantage is that
> you can't get the file from the fileserver --- you can't authenticate
> to it.
>
> if you wait until you have auth set up, you could use files from
> the fs, but you'd have one convention for entering passwords
> and another for entering everything else. (assuming all the
> chars in your password are typable with your keyboard and
> the standard layout interpretation.)
>
> so the only solution is to build the kbmap into the kernel.
>
> i'm not going to try this, so i might mess a few details up,
> but this is close to what you want to do.
>
> 1. use "kbmap=/boot/uk"
>
> 2. edit your terminal configuration. generally this is /sys/src/9/pc/pc.
> in the bootdir section add "/sys/lib/kbmap/uk"
>
> 3. make your kernel "mk 'CONF=pc' install"
>
> 4. copy /386/9pc to wherever you boot from. if you're
> changing the name of your kernel, then be sure to edit
> your plan9.ini, too.
>
> 5. reboot. after booting, you can verify that you've got
> it right by
> mount /srv/boot /n/boot
> lc /boot
> you should see a file named "uk" in /boot. (and your
> keyboard should work correctly.)
>
> - erik
>
>
>
>
next prev parent reply other threads:[~2008-07-17 21:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-15 19:47 Robert Hibberdine
2008-07-15 19:59 ` Francisco J Ballesteros
2008-07-16 20:46 ` Robert Hibberdine
2008-07-16 22:00 ` Pietro Gagliardi
2008-07-17 19:00 ` Robert Hibberdine
2008-07-17 19:11 ` andrey mirtchovski
2008-07-17 21:05 ` Robert Hibberdine
2008-07-17 19:12 ` erik quanstrom
2008-07-17 21:12 ` Robert Hibberdine [this message]
2008-07-16 22:21 ` Francisco J Ballesteros
2008-07-17 21:22 erik quanstrom
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=487FB5C7.5030908@ntlworld.com \
--to=bob.hibberdine@ntlworld.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).