Visit Our UNIX and Linux User Community

Linux and UNIX Man Pages

Test Your Knowledge in Computers #303
Difficulty: Easy
Normally sed is invoked like this: sed SCRIPT INPUTFILE ...
True or False?
Linux & Unix Commands - Search Man Pages

dtab(5) [bsd man page]

DTAB(5) 							File Formats Manual							   DTAB(5)

NAME
dtab - automatic system configuration device table (2BSD) DESCRIPTION
The dtab file contains a list of the devices that the autoconfig(8) program will attempt to attach to the system. Each line describes one device which may be present on the system; additional devices of the same type require additional lines. The line contains at least six fields separated by white space. Blank lines and comments can appear anywhere in the file except between fields; comments are delimited by `#' and new line. The fields are (in order): dev The device name, usually two characters unit Either a unit number or a `?' indicating automatic selection of unit numbers. addr The address of the device's first register, as a 16-bit octal number. vector The interrupt vector, in octal. BR The priority at which the device interrupts. handler(s) One or more routine names with which the interrupt vector is filled. EXAMPLE
# Device Configuration Table # Clock and console are pre-configured and should not be listed here # # Dev# Addr Vector Br Handler(s) # Comment lp ? 177514 200 4 lpio # lp-11 line printer ht 0 172440 224 5 htintr # tu 16 massbus tape xp ? 176700 254 5 xpio # xp driver dm ? 170500 310 4 dmin # dm11 dh modem control dh ? 160020 320 5 dhin dhou # dh11 terminal mux dz ? 160110 330 5 dzin dzdma # dz11 terminal mux FILES
/etc/dtab device table SEE ALSO
autoconfig(8) BUGS
/Etc/dtab is unique to the PDP-11 and 2BSD. 3rd Berkeley Distribution January 22, 1987 DTAB(5)

Check Out this Related Man Page

DH(4)							     Kernel Interfaces Manual							     DH(4)

NAME
dh - DH-11/DM-11 communications multiplexer SYNOPSIS
/sys/conf/SYSTEM: NDH dh_units # DH11; NDH is in units of boards (16 each) NDM dm_units # DM11; NDM is in units of boards (16 each) /etc/dtab: #Name Unit# Addr Vector Br Handler(s) # Comments dm ? 170500 310 4 dmintr # dm11 dh modem control dh ? 160020 320 5 dhrint dhxint # dh11 terminal mux major device number(s): raw: 3 minor device encoding: bits 0017 specify line on DH unit bits 0060 specify DH unit bit 0100 specify RTS/CTS (``hardware'') flowcontrol bit 0200 specifies non-blocking open (``CD always on'') DESCRIPTION
A dh-11 provides 16 communication lines; dm-11's may be optionally paired with dh-11's to provide modem control for the lines. If there are fewer dm-11's than dh-11's, the dm-11's are assumed to be paired with the first dm_units dh-11's. Each line attached to the DH-11 communications multiplexer behaves as described in tty(4). Input and output for each line may indepen- dently be set to run at any of 16 speeds; see tty(4) for the encoding. Bit 0200 of the minor device number for DH lines may be set to say that a line is not properly connected, and that the line should be treated as hard-wired with carrier always present. Thus creating the special character device node "3, 130" via mknod /dev/ttyh2 c 3 130 would cause line ttyh2 to be treated in this way. Bit 0100 of the minor device number enables RTS/CTS (also called ``hardware'') flow con- trol. It is enabled by adding 64 to the minor device number: mknod /dev/ttyh2 c 3 194 The dh driver monitors the rate of input on each board, and switches between the use of character-at-a-time interrupts and input silos. While the silo is enabled during periods of high-speed input, the driver polls for input 30 times per second. FILES
/dev/tty[h-k][0-9a-f] /dev/ttyd[0-9a-f] /dev/MAKEDEV script to create special files /dev/MAKEDEV.local script to localize special files SEE ALSO
tty(4), dtab(5), autoconfig(8) DIAGNOSTICS
dh%d NXM. No response from UNIBUS on a dma transfer within a timeout period. This has never been observed on a PDP-11 and is a carryover from the VAX driver when it was ported. It is not serious. dh%d %d overruns. The character input silo overflowed before it could be serviced. This message is only printed at line close time. It is not serious but does indicate that the system was not able to keep up with the data flow. 3rd Berkeley Distribution May 31, 1997 DH(4)

Featured Tech Videos