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

MKNOD(8)						    BSD System Manager's Manual 						  MKNOD(8)

NAME

     mknod -- make device special file

SYNOPSIS

     mknod [-F format] name [c | b] major minor
      [-F format] name [c | b] major unit subunit
      name [c | b] number
      name [p]

DESCRIPTION

     The mknod command creates device special files.  Normally the shell script /dev/MAKEDEV is used to create special files for commonly known
     devices; it executes mknod with the appropriate arguments and can make all the files required for the device.

     To make nodes manually, the required arguments are:

     name    Device name, for example ``sd'' for a SCSI disk on an HP300 or a ``pty'' for pseudo-devices.

     b | c | p
	     Type of device. If the device is a block type device such as a tape or disk drive which needs both cooked and raw special files, the
	     type is b.  All other devices are character type devices, such as terminal and pseudo devices, and are type c.  To create named pipes
	     the type p can be used.

     major   The major device number is an integer number which tells the kernel which device driver entry point to use.  To learn what major
	     device number to use for a particular device, check the file /dev/MAKEDEV to see if the device is known, or check the system depen-
	     dent device configuration file:

		   ``/usr/src/sys/conf/device.architecture''

	     (for example device.hp300).

     minor   The minor device number tells the kernel which one of several similar devices the node corresponds to; for example, it may be a spe-
	     cific serial port or pty.

     unit and subunit
	     The unit and subunit numbers select a subset of a device; for example, the unit may specify a particular SCSI disk, and the subunit a
	     partition on that disk.  (Currently this form of specification is only supported by the bsdos format, for compatibility with the
	     BSD/OS mknod(8) .)

     Device numbers for different operating systems may be packed in a different format.  To create device nodes that may be used by such an oper-
     ating system (e.g. in an exported file system used for netbooting), the -F option is used.  The following formats are recognized: native,
     386bsd, 4bsd, bsdos, freebsd, hpux, isc, linux, netbsd, osf1, sco, solaris, sunos, svr3, svr4 and ultrix.

     Alternatively, a single opaque device number may be specified.

SEE ALSO

     mkfifo(1), mkfifo(2), mknod(2), MAKEDEV(8)

HISTORY

     A mknod command appeared in Version 6 AT&T UNIX.  The -F option appeared in NetBSD 1.4.

NetBSD 1.4							September 11, 1998							NetBSD 1.4

Linux and UNIX Man Pages

makedev(8) [osf1 man page]

Check Out this Related Man Page