From:	CSBVAX::CSBVAX::MRGATE::"SMTP::MOORE.FAC.CS.CMU.EDU::DALE.MOORE"  6-MAR-1989 09:48
To:	MRGATE::"ARISIA::EVERHART"
Subj:	Re: multiple session driver


Date: 6 Mar 1989 09:47:10 EST
From: Dale.Moore@MOORE.FAC.CS.CMU.EDU
To: Everhart%arisia.decnet@GE-CRD.ARPA
CC: karney%ppc.mfenet@NMFECC.ARPA
Subject: Re: multiple session driver

Hi...

In a recent article on comp.os.vms you said

> using the CMU/KevinCarosso PTY driver as an intermediary...

I'm the guy at CMU who originally wrote it.  Kevin did work on it,
but then so did Dave Kashtan,  Mark London, Doug Davis and a host
of others.  It's just that Kevin was one of the loudest cheer leaders.
At least you did better than most.  Most folks just call it
Kevin Carosso's pseudo terminal driver.

Kevin is a very very bright guy.  But on one of his "Major changes
and upgrades" to the pty driver, he changed 6 lines of code, out of
several hundred.

Also, Kevin called me up on the phone one day, asked if this pseudo
terminal driver could be put in public domain.  I told him that I
wasn't sure.  It was ok with me, but CMU owned the code, and I would
have to get back to him.   A few weeks later, it was "Kevin Carosso's
public domain pseudo terminal driver."  Arghhhhhhh....  Just how
the hell can someone else place our work in public domain?

Today, DEC is releasing the pty executables with DECwindows.
And there is version skew all over the damn place.  Gandalf of
Canada has a version that they use for a LAT like piece of hardware.
Symbolics had a version for their VMS chaos code.
Lots of folks who have  gotten it have added their own bells 
and whistles.

Now DEC is adding their bells and whistles.  And there are so damn
many incompatible versions out there.  I wish DEC would have the
back bone to support it.  As it is right now,  lots of folks
are asking me to supply DEC's changes to them.  I've been able to
deduce the changes by looking at their executables and working back
to source.  But I might not be able to do that in the future.
I've tried getting DEC's source to my device driver, but DEC
is acting like the large slothful animal that it is.  I can't
get them to wake up.  By using debuggers and disassemblers
I now have sources that generate DEC's executables.

Just why am I telling you all this.  Damned if I know.  Maybe you'll
appreciate the information.  Maybe not.  The only thing I know is
that to call it Kevin Carosso's pseudo terminal driver is to cut
short all the other folks who have spent as much or more time than
Kevin working on that piece of software.

Dale Moore