[comp.sources.bugs] Who fixed the pty driver for SysV?

jay@splut.UUCP (Jay Maynard) (05/16/88)

I am in the process of cleaning up the pty driver for SysV, which was
posted to comp.sources.misc in NCR Tower-specific form and then cleaned
up and reposted here. I have made it work with Microport System V/AT,
and will be posting the cleaned-up version to comp.sources.misc as soon
as I finish documenting and cleaning.

Unfortunately, somewhere down the line, I have lost the person's name
who did the original generalization. I think he either works for TTI or
has the initials TTI...since that's what the comments in the code are
delimited with.

If you are this kind soul who saved me a LOT of work, or know for a
certainty who he is, please E-mail me so I don't steal the credit for
making it work.

-- 
Jay Maynard, EMT-P, K5ZC...>splut!< | GEnie: JAYMAYNARD  CI$: 71036,1603
uucp: {uunet!nuchat,hoptoad!academ!uhnix1,{ihnp4,bellcore}!tness1}!splut!jay
Never ascribe to malice that which can adequately be explained by stupidity.
Let's rename it talk.bizarre.Kent.Paul.Dolan.for.President.in.88!

michael@stb.UUCP (Michael) (05/27/88)

Here's a different question about the Sys 5 pty driver: How do you get it
to work on a system 3 machine? We don't have a struct ccblock, so the
routines for calling the line discipline routines don't work right.
Any helpers? Anyone written a system 3 (or version 7) device driver?
				Michael
: --- 
: Michael Gersten			 uunet.uu.net!denwa!stb!michael
:				 ihnp4!hermix!ucla-an!denwa!stb!michael
:				sdcsvax!crash!gryphon!denwa!stb!michael
: "Machine Takeover? Just say no."
: "Sockets? Just say no."     <-- gasoline