From: Andreas Dilger <adilger@turbolinux.com>
To: Jens Petersohn <jkp@mccoy.penguinpowered.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Q] Remote serial ports?
Date: Fri, 15 Dec 2000 13:27:48 -0700 (MST) [thread overview]
Message-ID: <200012152027.eBFKRmh07217@webber.adilger.net> (raw)
In-Reply-To: <200012151514.JAA29931@mccoy.penguinpowered.com> "from Jens Petersohn at Dec 15, 2000 09:14:57 am"
Jens Petersohn writes:
> I have an application in which it would be useful to have access to
> remote serial ports as if they where local ports.
>
> Machine A has several serial ports on it connected to various
> special types of devices in a locked machine room.
>
> Developers on workstation B wants to execute an application that
> communicates with the special devices, but can only do so via
> /dev/ttySXX. The developer however (for various reasons) cannot
> directly log into Machine A.
>
> Is there some software that would allow "remote forwarding" of
> serial ports? I.e. a driver that emulates a serial port on
> machine B and forwards the read/write/ioctl operations to machine A?
> Does this exist? Is it possible to implement if it doesn't?
> Am I overlooking something obvious?
Please see the posting on l-k today "[NEW DRIVER] New user space serial port"
which does just what you want. Just-in-time kernel development has arrived.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2000-12-15 20:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-15 15:14 Jens Petersohn
2000-12-15 20:27 ` Andreas Dilger [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=200012152027.eBFKRmh07217@webber.adilger.net \
--to=adilger@turbolinux.com \
--cc=jkp@mccoy.penguinpowered.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®