/dev/stdin driver

[Chris Torek]

>In article <8167 at ncoast.UUCP>, allbery at ncoast.UUCP (Brandon S. Allbery) writes:
>>... In other words, the usual 4.xBSD-source elitism.)

In article <1186 at mcgill-vision.UUCP> mouse at mcgill-vision.UUCP (der Mouse)
writes:
>... if you check back and look at the original postings on this
>issue, the /dev/stdin point was first brought up as follows:

[This from Andrew Hume]
>>	a unix without /dev/stdin is largely bogus but as a sop to the poor
>>	barstards having to work on BSD, gre will support -
>>	as stdin (at least for a while).
[He is Australian, so he is allowed to talk like this :-)]

>With phrasing like that, I can hardly blame Chris for rising to the
>defense of his driver.  And note the "BSD" phrase: that's the context
>in which Chris said there was no excuse for complaining about not
>having /dev/stdin.  And in that context, I agree with him.

Actually, it is Fred Blonder's driver; he wrote it before anyone
here heard of /dev/stdin in V8 Unix.

>And there's no call for complaints about source elitism.  My /dev/stdin
>driver can be added to a binary distribution; surely Chris' can too.

You will need to know the conventions for your system, but yes, it
should not be hard.  Since it only has an `open' routine, it is probably
the simplest driver in the Unix world anyway.
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7163)
Domain:	chris at mimsy.umd.edu	Path:	uunet!mimsy!chris