Home | History | Annotate | Download | only in bnu
      1 #
      2 # Copyright 2005 Sun Microsystems, Inc.  All rights reserved.
      3 # Use is subject to license terms.
      4 #
      5 # CDDL HEADER START
      6 #
      7 # The contents of this file are subject to the terms of the
      8 # Common Development and Distribution License, Version 1.0 only
      9 # (the "License").  You may not use this file except in compliance
     10 # with the License.
     11 #
     12 # You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE
     13 # or http://www.opensolaris.org/os/licensing.
     14 # See the License for the specific language governing permissions
     15 # and limitations under the License.
     16 #
     17 # When distributing Covered Code, include this CDDL HEADER in each
     18 # file and include the License file at usr/src/OPENSOLARIS.LICENSE.
     19 # If applicable, add the following below this CDDL HEADER, with the
     20 # fields enclosed by brackets "[]" replaced with your own identifying
     21 # information: Portions Copyright [yyyy] [name of copyright owner]
     22 #
     23 # CDDL HEADER END
     24 #
     25 #ident	"%Z%%M%	%I%	%E% SMI"
     26 
     27 # Some sample entries:
     28 # NOTE - all lines must have at least 5 fields 
     29 #    use '-' for unused fields
     30 # The Devices file is used in conjunction with the Dialers file.
     31 # Types that appear in the 5th field must be either built-in
     32 #  functions (801, Sytek, TCP, Unetserver, DK)
     33 #  or standard functions whose name appears in the first
     34 #  field in the Dialers file.
     35 # Two escape characters may appear in this file:
     36 # - \D which means don't translate the phone #/token
     37 # - \T translate the phone #/token using the Dialcodes file
     38 # Both refer to the phone number field in the Systems file (field 5)
     39 # \D should always be used with entries in the Dialers file, since the
     40 # Dialers file can contain a \T to expand the number if necessary.
     41 # \T should only be used with built-in functions that require expansion
     42 # NOTE: - if a phone number is expected and a \D or \T is not present
     43 #	a \T is used for a built-in, and \D is used for an entry
     44 #	referencing the Dialers file. (see examples below)
     45 #
     46 #
     47 # ---Standard modem line
     48 # ACU cua/b - 2400 hayes
     49 # or
     50 # ACU cua/b - 2400 hayes \D
     51 #
     52 # ---A direct line so 'cu -lcua/b' will work
     53 # Direct cua/b - 9600 direct
     54 #
     55 # ---A ventel modem on a develcon switch (vent is the token given to
     56 #	the develcon to reach the ventel modem)
     57 # ACU cua/b - 1200 develcon vent ventel
     58 # ACU cua/b - 1200 develcon vent ventel \D
     59 #
     60 # ---To reach a system on the local develcon switch
     61 # Develcon cua/b - Any develcon \D
     62 #
     63 # ---Access a direct connection to a system
     64 # systemx term/00 - Any direct
     65 #
     66 # where the Systems file looks like
     67 # systemx Any systemx 1200 unused  "" in:-\r\d-in: nuucp word: nuucp
     68 #	(The third field in Systems matches the first field in Devices)
     69 #
     70 # ---To connect to any system on the DATAKIT VCS network
     71 # DK DK 0 Any DK \D
     72 #
     73 # ---To connect to a system on a Datakit in nj/ho
     74 # DKho - uucp Any DK nj/ho/\D
     75 #
     76 # ---To use an ACU that is connected to Datakit that DK does not understand
     77 #	how to talk to directly
     78 # ACU - 0 Any DK vent ventel \D
     79 #
     80 # ---To use a dialer that the Datakit understands how to chat with
     81 #	This is a special case where the translation must be done by the
     82 #	Devices file processing.
     83 # ACU DKacu 0 Any DK py/garage/door.\T
     84 #
     85 
     86 TCP,et - - Any TCP -
     87 
     88 ########	AT&T Transport Interface
     89 #
     90 # ---To use a STREAMS network that conforms to the AT&T Transport Interface
     91 #	with a direct connection to login service (i.e., without
     92 #	explicitly using the Network Listener Service dial script):
     93 #
     94 # networkx,eg devicex - - TLIS \D
     95 #
     96 #	The Systems file entry looks like:
     97 #
     98 # systemx Any networkx - addressx in:--in: nuucp word: nuucp
     99 #
    100 #	You must replace systemx, networkx, addressx, and devicex with system
    101 #	name, network name, network address and network device, respectively.
    102 #	For example, entries for machine "sffoo" on a STARLAN NETWORK might
    103 #	look like:
    104 #		sffoo Any STARLAN - sffoo in:--in: nuucp word: nuucp
    105 #	and:
    106 #		STARLAN,eg starlan - - TLIS \D
    107 #
    108 # ---To use a STREAMS network that conforms to the AT&T Transport Interface
    109 #	and that uses the Network Listener Service dial script to negotiate
    110 #	for a server:
    111 #
    112 # networkx,eg devicex - - TLIS \D nls
    113 #
    114 #
    115 # ---To use a non-STREAMS network that conforms to the AT&T Transport 
    116 #	Interface and that uses the Network Listener Service dial script
    117 #	to negotiate for a server:
    118 #
    119 # networkx,eg devicex - - TLI \D nls
    120 #
    121 ########
    122 #
    123 #
    124 # NOTE: blank lines and lines that begin with a <space>, <tab>, or # are 
    125 #		ignored.
    126 #	protocols can be specified as a comma-subfield of the device type
    127 #		either in the Devices file (where device type is field 1)
    128 #		or in the Systems file (where it is field 3).
    129 #
    130 ########
    131 #
    132 ACU cua/b - Any hayes
    133 Direct cua/b - Any direct
    134