Path: utzoo!utgpu!water!watmath!clyde!rutgers!lll-lcc!mordor!sri-spam!zodiac!ucbcad!ucbvax!LBL.GOV!nagy%warner.hepnet
From: nagy%warner.hepnet@LBL.GOV (Frank J. Nagy, VAX Wizard & Guru)
Newsgroups: comp.os.vms
Subject: Driver naming (was RE: Carosso's pseudo-terminal driver)
Message-ID: <880106171131.24200cc4@LBL.Gov>
Date: 7 Jan 88 01:11:31 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 21

> 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.
     
Seems lots of people are having this problem.  OK, try this as a way of
avoiding conflict with Digital device names: almost all Digital devices
use 2 character names (TT, TP, PA, etc.) and a few use 3 (NET and PTY,
this later seems to be a pseudo-terminal driver which is part of the
DECTest/Manager layered product - no documentation on using it directly
however :-().  Therefore, select a 4, 5 or longer character name for
the device and driver - maybe YTPDRIVER (yep, that's PTY backwards :-).
Device names can be use to 15 characters long; I've written a driver
called UICDRIVER (for the AMD-9519 Universal Interrupt Controller
chip) which supports devices named VAXQA0, VAXQB0, etc. on some
of our systems.

= Frank J. Nagy   "VAX Guru & Wizard"
= Fermilab Research Division EED/Controls
= HEPNET: WARNER::NAGY (43198::NAGY) or FNAL::NAGY (43009::NAGY)
= BitNet: NAGY@FNAL
= USnail: Fermilab POB 500 MS/220 Batavia, IL 60510