public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Raphael Jacquot <raphael.jacquot@imag.fr>
To: "P.Manohar" <pmanohar@lantana.cs.iitm.ernet.in>,
	linux-kernel@vger.kernel.org, industeqsite@industeqsite.com
Subject: Re: remote keyboard
Date: Thu, 12 May 2005 07:04:00 +0200	[thread overview]
Message-ID: <4282E3C0.8080604@imag.fr> (raw)
In-Reply-To: <Pine.LNX.4.60.0505121017090.31256@lantana.cs.iitm.ernet.in>

P.Manohar wrote:
> 
> " I am planning to have remote keyboard to control the operations on a
>  particular target. To explain in detail, I will have a PC with keyboard,
>  mouse etc and this PC will be connected to another PC(Remote) via
> Ethernet.
> Instead of using the local keyboard input, I want sent the keyboard keys
> from the remote system (another PC via Ethernet) and use it as if it from
>  the local keyboard.
> 
> My Plan
>  I am planning to use the Linux keyboard driver and read the keyboard
> buffer
> from the remote PC and send it to the target PC, and in the target PC
>  whatever the key code I have received through the Ethernet I will put it
> into the local keyboard buffer using the Linux keyboard driver IOCTLs.
> 
>  Can anybody tell me is this acceptable "
> 
> 
> Hai,
>    The above message appeared in kernel-mailing list,
>  I am also involved in the same problem.
> How to put characters into keyboard buffer using the Linux keyboard
> driver IOCTLs?
> 
> If anybody knows about it please guide me.

are you using a graphical (Xwindow) application ?
in that case there is absolutely no point in doing that kind of horrible
hack, as the XWindow System is network transparent, that is, you can run
the application on machine A, and have it display and be controlled on
machine B
you can even use the ssh secure shell to securely do so, in an encrypted
manner.


  reply	other threads:[~2005-05-12  5:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-12  4:51 remote keyboard P.Manohar
2005-05-12  5:04 ` Raphael Jacquot [this message]
2005-05-12 14:14   ` Joel Jaeggli
2005-05-12  8:12 ` Jan-Benedict Glaw
2005-05-12 17:42   ` Timothy Ball

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=4282E3C0.8080604@imag.fr \
    --to=raphael.jacquot@imag.fr \
    --cc=industeqsite@industeqsite.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmanohar@lantana.cs.iitm.ernet.in \
    /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