9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: kokamoto@hera.eonet.ne.jp
To: 9fans@hera.eonet.ne.jp
Subject: [9fans] kbdputc() in devcons.c in 9front?
Date: Thu, 17 Jul 2014 10:59:20 +0900	[thread overview]
Message-ID: <c7eda64ae294e2710da9be93044b8320@jitaku.localdomain> (raw)

I'm checking how I should build my Plan9 system
in my home environment.   As I said before, we
have to save power as possible as we can (no
nuclear power energy here).   If I choose one
file/auth/cpu server machine, Plan9front may be
fastest.   However, I have here one serious problem.
Ktrans does not work on it.

You, 9front developpers, created kbdfs, and
lost kbdputc() in port/devcdons.c.   Most of
pc/kbd.c stuffs are driven out to user space, kbdfs.

In lab's or 9atom's distribution, I can have
/rc/bin/Kanji, like:
	#!/bin/rc

	pipefile -r ktrans /dev/cons
	rio -i $home/lib/windows </dev/cons

This assumes that the keyboard input from
stdin, and produces kanji translated character to
/dev/cons.

What is the merrit to create kbdfs?
I cann't see it, but only demerit like above.

Kenji




             reply	other threads:[~2014-07-17  1:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-17  1:59 kokamoto [this message]
2014-07-17  7:39 ` cinap_lenrek
2014-07-17 16:44   ` erik quanstrom
2014-07-17  8:02 ` cinap_lenrek
2014-07-17 16:15   ` erik quanstrom
2014-07-17 17:54     ` sl
2014-07-17 18:41     ` cinap_lenrek
2014-07-17 10:45 ` Steve Simon
2014-07-17 10:58 ` Steffen Nurpmeso
2014-07-17 12:17 ` cinap_lenrek
2014-07-18  0:13   ` kokamoto
2014-07-18  0:16     ` cinap_lenrek
2014-07-19 12:56 ` kokamoto

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=c7eda64ae294e2710da9be93044b8320@jitaku.localdomain \
    --to=kokamoto@hera.eonet.ne.jp \
    --cc=9fans@hera.eonet.ne.jp \
    /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).