Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!bloom-beacon!bu-cs!purdue!decwrl!decvax!ima!cfisun!lakart!dg
From: dg@lakart.UUCP (David Goodenough)
Newsgroups: comp.unix.wizards
Subject: Re: Reading from stderr
Message-ID: <507@lakart.UUCP>
Date: 19 Apr 89 16:32:13 GMT
References: <5451@lynx.UUCP>
Distribution: na
Organization: Lakart Corporation, Newton, MA
Lines: 18

From article <5451@lynx.UUCP>, by m5@lynx.uucp (Mike McNally):
> Oh well, I guess I should change the question a little:  what's the
> advantage of having "/dev/tty" behave the way it does in this respect?
> That is, would a massive catastrophe occur if a file descriptor
> returned from an open request on "/dev/tty" was a real honest-to-gosh
> dup of the control tty file descriptor?

The only real problem would be for daemons and the like which have no
controlling tty. But I suppose that open / the /dev/tty driver could be
made clever enough to make this work as well (i.e. select action based on
whether the process has a controlling tty or not).

Of course _REAL_ operating systems (like I run on pallio) have
stdkbd defined, so I can _ALWAYS_ get at the terminal input line
when I need it. :-) :-) :-) :-) :-)


		Comments anyone?
-- 
	dg@lakart.UUCP - David Goodenough		+---+
						IHS	| +-+-+
	....... !harvard!xait!lakart!dg			+-+-+ |
AKA:	dg%lakart.uucp@xait.xerox.com		  	  +---+