Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mandrill!hal!ncoast!allbery From: allbery@ncoast.UUCP (Brandon S. Allbery) Newsgroups: comp.unix.wizards Subject: Re: /dev/stdin driver Message-ID: <8219@ncoast.UUCP> Date: 5 Jul 88 17:41:15 GMT References: <7962@alice.UUCP> <5826@umn-cs.cs.umn.edu> <8167@ncoast.UUCP> <1186@mcgill-vision.UUCP> <12169@mimsy.UUCP> Reply-To: allbery@ncoast.UUCP (Brandon S. Allbery) Followup-To: comp.unix.wizards Organization: Cleveland Public Access UN*X, Cleveland, Oh Lines: 17 As quoted from <12169@mimsy.UUCP> by chris@mimsy.UUCP (Chris Torek): +--------------- | >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. +--------------- So can anyone tell me how to add it to a System III kernel -- what changes might be needed to make it work (I *do* know how to actually add the driver, but SysIII isn't SysV)? [We may move to System V or even BSD in the future -- money permitting. Don't push us unless you intend to pay for it.] -- Brandon S. Allbery, uunet!marque!ncoast!allbery DELPHI: ALLBERY For comp.sources.misc send mail to ncoast!sources-misc