Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!yetti!geac!daveb
From: daveb@geac.UUCP
Newsgroups: comp.unix.wizards
Subject: Separating input (tty) streams.
Message-ID: <1757@geac.UUCP>
Date: Mon, 2-Nov-87 12:10:41 EST
Article-I.D.: geac.1757
Posted: Mon Nov  2 12:10:41 1987
Date-Received: Tue, 3-Nov-87 02:39:32 EST
References: <15973@topaz.rutgers.edu> <1987Oct29.152901.2784@utfyzx.uucp>
Reply-To: daveb@geac.UUCP (Dave Collier-Brown)
Organization: The little blue rock next to that twinkly star.
Lines: 27
Keywords: tty input streams sockets


  Although I admit to knowing a fair bit about the history and
philosophy of Unix, I must admit puzzlement in one fairly large and
obvious (spelled "embarassing") area.

  I can't for the life of me figure out how to separate material
written to "/dev/ttyXX" by another user or process from material
written by my shell or editor process.
  What I wish to do is leave my /dev/tty writable, but direct
it to a particular program, while my shell and editor happily use
the real tty to talk to me, and can talk to the program listening
for my output.

  I can think of several ways to approach this:
	1) literally: put a FIFO or socket in the path from
/dev/ttyXX to me, and feed that to a program.
	2) figuratively: use an existing Streams or Sockets facility
to point the streams of text where I want them.
	3) kludgily (n ways).

  Suggestions re algorithms, please: I will collect them, post and
(if implemented) post the results.
-- 
 David Collier-Brown.                 {mnetor|yetti|utgpu}!geac!daveb
 Geac Computers International Inc.,   |  Computer Science loses its
 350 Steelcase Road,Markham, Ontario, |  memory (if not its mind)
 CANADA, L3R 1B3 (416) 475-0525 x3279 |  every 6 months.