From: alex <alex9-ml@proton.me>
To: 9front@9front.org
Subject: Re: [9front] making permanent changes to /dev/kbmap
Date: Wed, 26 Jun 2024 06:52:32 +0000 [thread overview]
Message-ID: <SC2zxP0SZgYEjbH4X0-BYUjhO9I5cPll-ul2XafCtX5dbj9URLjvgqvy8jvAtffoG8wEwF8q5rN86G4W0DNhdriLTpETkEYXCbfTYaX3k3w=@proton.me> (raw)
In-Reply-To: <FBA834B6347C094FBE156862079CA04C@felloff.net>
Hello cinap,
thank you very much!
I'm not sure if I implemented your last suggestion correctly, but it works:
Since I didn't know how to customize /sys/src/9/boot/bootfs.proto, I added a kbmap to /sys/lib/kbmap/, specified it in plan9.ini and rebuilt the kernel.
This worked wonderfully, thanks again!
Best regards,
Alex
cinap_lenrek@felloff.net <cinap_lenrek@felloff.net> schrieb am Sonntag, 23. Juni 2024 um 13:17:
> Adding it to $home/lib/profile is one way,
> but remember that this is run also on rcpu
> logins. Of course, you can make sure to only
> apply it when ~ $service terminal and
> ~ $terminal reform ...
>
> Probably better approach is adding that to
> /cfg/$sysname/termrc or... Which only runs
> at boot before the login.
>
> Or make a "reform" keyboard map file and add it to
> /sys/src/9/boot/bootfs.proto,
> including it into the kernel's bootfs.paq
> file system:
>
> Then set kbmap=reform in your plan9.ini.
>
> see /sys/src/9/boot/bootrc:
>
> if(! ~$#kbmap 0){
> if(test -f /sys/lib/kbmap/$kbmap){
> echo 'setting kbmap to' $kbmap
> cat /sys/lib/kbmap/$kbmap >/dev/kbmap
>
> }
> }
>
> That way, the keyboard will behave even before
> the file-system is mounted.
>
> --
> cinap
prev parent reply other threads:[~2024-06-26 6:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-22 14:29 alex
2024-06-23 11:17 ` cinap_lenrek
2024-06-26 6:52 ` alex [this message]
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='SC2zxP0SZgYEjbH4X0-BYUjhO9I5cPll-ul2XafCtX5dbj9URLjvgqvy8jvAtffoG8wEwF8q5rN86G4W0DNhdriLTpETkEYXCbfTYaX3k3w=@proton.me' \
--to=alex9-ml@proton.me \
--cc=9front@9front.org \
/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).