From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <deabf8040afa719a1df3718a27bc5d9c@quanstro.net>
To: 9fans@9fans.net
From: erik quanstrom <quanstro@quanstro.net>
Date: Thu, 17 Jul 2008 15:12:09 -0400
In-Reply-To: <487F96EB.4010906@ntlworld.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] setting up a differnet keyboard
Topicbox-Message-UUID: eaf3476c-ead3-11e9-9d60-3106f5b1d025

> 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