carl@CITHEX.CALTECH.EDU (Carl J Lydick) (01/06/88)
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?
ABSTINE@CLVMS.CLARKSON.EDU (AB Stine) (01/06/88)
I got bit by it (by PSI V4.1 actually, which now has its own TPdriver).
I use it along with the CMU TCP package. I decided to call it TNdriver,
but there is no guarantee that is unique either. DEC has alot of drivers.
art stine
network engr
clarkson ukvc@nrcvax.UUCP (Kevin Carosso) (01/10/88)
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.