Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!decwrl!labrea!rutgers!im4u!ut-sally!utah-cs!utah-gr!uplherc!nrc-ut!nrcvax!kvc
From: kvc@nrcvax.UUCP (Kevin Carosso)
Newsgroups: comp.os.vms
Subject: Re: Carosso's pseudo-terminal driver
Message-ID: <1342@nrcvax.UUCP>
Date: 10 Jan 88 03:36:02 GMT
References: <880105190618.06p@CitHex.Caltech.Edu>
Reply-To: kvc@minnie.UUCP (Kevin Carosso)
Organization: Network Research Corp.  Oxnard, CA
Lines: 14

In article <880105190618.06p@CitHex.Caltech.Edu> carl@CITHEX.CALTECH.EDU (Carl J Lydick) writes:
>Well, Kevin Carosso renamed his pseudo-terminal driver from PTDRIVER to
>TPDRIVER to avoid a conflict with TMSCP devices.  Now DEC is using the name
>TPDRIVER as the terminal class driver for use with PSI.  Anybody got any
>good ideas for a new name?  Kevin, are you out there anywhere?

Yeah, I'm here...  Anyone got a good idea for a new name?  Someone
on the CMU-TEK-TCP mailing list chose either NT or TN (I don't remember
which).  Other suggestions were to use something other than a simple
two-character device name.  For example, the implementation of named
pipes you get with the DEC/Shell uses device names of the form
PIPE0:, PIPE1:, etc...  Can anyone tell me what the real rules are for
device names?  Obviously, you aren't restricted to two-letters, another
letter, and a number.