Visit Our UNIX and Linux User Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

makedev(8) [osf1 man page]

MAKEDEV(8)						      System Manager's Manual							MAKEDEV(8)

NAME
MAKEDEV - makes system special files SYNOPSIS
/dev/MAKEDEV [argument] [device-name?...] DESCRIPTION
The MAKEDEV shell script is normally used to install special files. It resides in the /dev directory, the normal location of special files. Arguments to MAKEDEV are usually of the form device-name? where device-name is one of the supported devices listed in Section 7 of the Reference Pages and ? is a logical unit number. The argument operand is one of the following special arguments that create assorted col- lections of devices: Creates all standard device files for all systems. Standard devices for Alpha systems (in the order they are created) are as follows: klog, kcon, kbinlog, kmem, mem, null, vmzcore, console, ws0, mouse0, keyboard0, tty, pty0, pty1, ptmx, cam, audit, prf, pfcntr, zero, snmpinfo, lockdev, and sysdev0. Creates a set of 16 LAT device special files, one for each LAT terminal device. The n specifies the set option. The set option range is 0 to 38. Specifying lat38 creates 12 LAT device special files. Creates groups of pseudoterminal device special files, as follows: Cre- ates pty0 to pty22. Creates pty23 to pty45. Creates pty46 to pty56. Creates pty57 to pty64. Creates pty65 to pty72. Creates pty73 to pty80. Creates pty81 to pty88. Creates pty89 to pty96. Creates pty97 to pty101. The # specifies the group of pseudoterminal device special files created. Creates a group of packet filter device special files, as follows: Creates pfilt0 to pfilt63. Creates pfilt0 to pfilt63. Creates pfilt0 to pfilt127. Creates pfilt0 to pfilt255. Creates pfilt0 to pfilt511. Creates pfilt0 to pfilt1023. Creates pfilt0 to pfilt2047. Creates pfilt0 to pfilt3071. Creates pfilt0 to pfilt4095. The # specifies the number of ppacket filter device special files created. Creates those devices specific to the local site. This request causes the shell file /dev/MAKEDEV.local to be executed. This file must exist prior to using the local argument. Site spe- cific commands, such as those used to setup dialup lines as ttyd? and to create device special files for all non-Compaq devices, should be included in this file. Because all devices are created using mknod(8) this shell script is useful only to the superuser. NOTES
The MAKEDEV script installs files in the current working directory. Although device special files can be located anywhere on the system, they are usually created in the /dev directory, since this is where most applications expect to find them. Refer to the dsfmgr(8) reference page for information on the Device Special File Manager program. ERRORS
Either self-explanatory, or generated by one of the programs called from the script. Use sh -x MAKEDEV in case of trouble. SEE ALSO
Commands: config(8), dsfmgr(8), mknod(8) Interfaces: intro(7), packetfilter(7), pty(7) MAKEDEV(8)

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