MKDEV(1M) Domain/OS SysV MKDEV(1M)
NAME
/etc/mkdev - make device files
SYNOPSIS
mkdev device_directory [-d devno_file] [all | console | display | tty |
null | nuls | logd | sio | smt | pad | pio | pty | dsk | mt |
global_devices | crp | cdrom | ac]
DESCRIPTION
mkdev creates device files. device_directory is usually /dev. -d
devno_file can be used to specify a device number-to-manager mapping
file; the default is `node_data/device_numbers.
If no additional arguments are specified, then all device files which do
not exist are created (except for Optical Disk Library System devices--
see below). On completion, the version number of the current mkdev
executable is recorded in the file device_directory/.mkdev.
If arguments for specific devices are specified, then just those
corresponding device files will be deleted and recreated. If the all
argument is specified, then all device files will be deleted and
recreated.
The ac argument generates several hundred device files that are needed
only on HP Series 6300 Model 20GB/A Optical Disk Library System server
nodes. To create the Optical Disk Library System devices, you must
specify the ac argument on the command line. Using mkdev with no
arguments or with the all argument creates every device file except those
for the Optical Disk Library System.
NOTE
In a UNIX environment, the `node_data directory must be specified as
\`node_data.
BUGS
If you run mkdev on a DN10000 workstation and specify a device_directory
argument on a Motorola 680x0 workstation, or vice-versa, mkdev will not
create the correct number of pad devices. mkdev will create the correct
number of pad devices only if you build a /dev directory by running mkdev
on a machine of similar type.
DIAGNOSTICS
Should be self-explanatory.
FILES
`node_data/device_numbers Default device number mapping file
SEE ALSO
mkdevno(1M), mkdsk(1M), mknod(1M).