From: Mikado <mikado4vn@gmail.com>
To: Petr Vandrovec <vandrove@vc.cvut.cz>
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>,
Glynn Clements <glynn@gclements.plus.com>,
linux-kernel@vger.kernel.org,
linux-c-programming@vger.kernel.org
Subject: Re: Virtual Serial Port
Date: Mon, 27 Mar 2006 10:29:48 +0700 [thread overview]
Message-ID: <44275C2C.9010507@gmail.com> (raw)
In-Reply-To: <4426E303.9000701@vc.cvut.cz>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Petr Vandrovec wrote:
> Although it is quite irrelevant to LKML (you may want to visit
> www.vmware.com/community/index.jspa and ask there...), you can connect
> guest's serial port also to Unix socket - and in such situation you need
> virtual serial port driver only if 'host - application' does not know
> how to use /dev/tty* (for unix socket <-> /dev/ptyp* app look at
> http://platan.vc.cvut.cz/ftp/pub/vmware/serpipe.tar.gz).
> Petr
Thank Petr. It also works well. That program acts as a data proxy
between unix socket and /dev/ptyp*. Yesterday I wrote a similar program
that read/write vmware's server unix sock then forward/backward data
to/from /dev/ptyp0 but it didn't work. Maybe my program has problem.
Thanks again.
Mikado
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFEJ1wsNWc9T2Wr2JcRArmmAJ483BmLFrY+aIR71u/BQH+XCs8tIQCfZGs1
uTwfbeYTsFg0Iq9/FL/82I4=
=dgch
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2006-03-27 3:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-25 17:49 Virtual Serial Port Mikado
2006-03-25 18:47 ` Jan Engelhardt
2006-03-26 2:23 ` Mikado
2006-03-26 3:27 ` Anderson Lizardo
2006-03-26 7:24 ` Joshua Hudson
2006-03-26 9:31 ` Jan Engelhardt
2006-03-26 17:09 ` Mikado
2006-03-26 18:52 ` Petr Vandrovec
2006-03-27 3:29 ` Mikado [this message]
2006-03-26 16:07 ` Glynn Clements
2006-03-27 11:25 ` Holy Aavu
2006-03-27 17:29 ` Glynn Clements
2006-03-28 5:53 ` Holy Aavu
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=44275C2C.9010507@gmail.com \
--to=mikado4vn@gmail.com \
--cc=glynn@gclements.plus.com \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-c-programming@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vandrove@vc.cvut.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.