From: Hiroki Tamakoshi <hiroki-t@is.aist-nara.ac.jp>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] keyboard mappings
Date: Tue, 20 Jun 2000 12:57:11 +0900 [thread overview]
Message-ID: <lzoitv5m2co.fsf@migi.aist-nara.ac.jp> (raw)
In-Reply-To: <200006191541.LAA27258@cse.psu.edu> (presotto@plan9.bell-labs.com's message of "Mon, 19 Jun 2000 16:06:30 GMT")
presotto@plan9.bell-labs.com writes:
> (http|ftp)://plan9.bell-labs.com/who/presotto/kbdmap.c
>
> maps keyboard characters. It has to be started before rio.
Please show me the correct usage of kbdmap.
I compiled kbdmap.c to kbdmap, put in my home directory.
Then inserted
kbdmap
before
exec rio
in lib/profile($service = terminal).
I rebooted the system and login, which cause trouble on rio.
Rio cannot open the display. Here is the error messages.
rio: can't open dislplay: initdisplay: /dev/draw/new: file already open for I/O
init: rc exit status: rio 10: rio 64: display open
next prev parent reply other threads:[~2000-06-20 3:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-19 15:41 presotto
2000-06-20 3:57 ` Hiroki Tamakoshi [this message]
2000-06-19 19:32 mike
2000-06-20 13:05 presotto
2000-06-20 15:14 Russ Cox
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=lzoitv5m2co.fsf@migi.aist-nara.ac.jp \
--to=hiroki-t@is.aist-nara.ac.jp \
--cc=9fans@cse.psu.edu \
/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).