tset reads stderr??

[Ron Kuris]

I wrote my own front-end getty a while back and had trouble using
'tset'.  Basically, it would never ask for the correct terminal
type.  I found out that it was reading stderr, which my front-end
getty opened for write-only (mode O_WRONLY).

Is there a good reason for this?  Wasn't there a discussion a while
back about reading from stdout, stderr?  If so, could someone
summarize?

Email only please -- save precious bandwidth!
-- 
+-------------------------------------------+
| {unify|sactoh0}!rdk386!ron (Ron Kuris)    |
| uucp now, cu later.                       |
+-------------------------------------------+