> > Based on the M_READ definition in the original AT&T documentation, it > > seems like a bug to me. FWIW, it dates back to the introduction of > > M_READ in SVR3.2. > > Furthermore, upon examination of the code, the only driver I can find > that actually enables M_READ delivery is ecpp. The various pty drivers > "handle" it, but none of them seem to configure it via M_SETOPTS. > > Would anyone complain too loudly if I "fixed" this bug? It would make > my life considerably simpler.
I doubt anyone would object. -- meem _______________________________________________ networking-discuss mailing list [email protected]
