mknod(1m) [opensolaris man page]

mknod(1M)						  System Administration Commands						 mknod(1M)

NAME

       mknod - make a special file

SYNOPSIS

       mknod name b major minor

       mknod name c major minor

       mknod name p

DESCRIPTION

       mknod makes a directory entry for a special file.

OPTIONS

       The following options are supported:

       b    Create a block-type special file.

       c    Create a character-type special file.

       p    Create a FIFO (named pipe).

OPERANDS

       The following operands are supported:

       major	The major device number.

       minor	The  minor  device  number; can be either decimal or octal. The assignment of major device numbers is specific to each system. You
		must be the super-user to use this form of the command.

       name	A special file to be created.

USAGE

       See largefile(5) for the description of the behavior of mknod when encountering files greater than or equal to 2 Gbyte ( 2^31 bytes).

ATTRIBUTES

       See attributes(5) for descriptions of the following attributes:

       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE	     |	    ATTRIBUTE VALUE	   |
       +-----------------------------+-----------------------------+
       |Availability		     |SUNWcsu			   |
       +-----------------------------+-----------------------------+

SEE ALSO

       ftp(1), in.ftpd(1M), mknod(2), symlink(2), attributes(5), largefile(5)

NOTES

       If mknod(2) is used to create a device, the major and minor device numbers are always interpreted by the kernel running on that machine.

       With the advent of physical device naming, it would be preferable to create a symbolic link to the physical name  of  the  device  (in  the
       /devices subtree) rather than using mknod.

SunOS 5.11							    16 Sep 1996 							 mknod(1M)

mknod(1M)																 mknod(1M)

NAME

       mknod - create special files

SYNOPSIS

       name major minor

       name major minor

       name

DESCRIPTION

       The command creates the following types of files:

	      o  Character device special file (first form),
	      o  Block device special file (second form),
	      o  FIFO file, sometimes called a named pipe (third form).

       name  is  the  path  name  of the file to be created.  The newly created file has a default mode that is readable and writable by all users(0666), but the mode is modified by the current setting of the user's file mode creation mask (see umask(1)).

   Character and Block Special Files
       Character device special files are used for devices that can transfer single bytes at a time, such  as  nine-track  magnetic  tape  drives,
       printers, plotters, disk drives operating in "raw" mode, and terminals.	To create a character special file, use the argument.

       Block  device  special  files are used for devices that usually transfer a block of data at a time, such as disk drives.  To create a block
       device special file, use the argument.

       The remaining arguments specify the device that will be accessible through the new special file:

	      major	The major number specifies the major device type (for example, the device driver number).

	      minor	The minor number specifies the device location, which is typically, but not always, the unit, drive, and/or line number.

       The major and minor values can each be specified in hexadecimal, octal, or decimal, using C language conventions (decimal: no leading zero;
       octal: leading zero; hexadecimal: leading

       The assignment of major and minor device numbers is specific to each HP-UX system.  Refer to the System Administrator manuals supplied with
       your system for details.

       Only users who have appropriate privileges can use to create a character or block device special file.

   FIFO files
       To create a FIFO (named pipe or buffer) file, use the argument.	You can also use the command for this purpose (see mkfifo(1)).	All  users
       can use to create FIFO files.

WARNINGS

   Access Control Lists
       In  HFS	file  systems, optional ACL entries can be added to special files and FIFOs with the command (see chacl(1)).  In JFS file systems,
       optional ACL entries can be added to special files and FIFOs with the command (see setacl(1)).  However,  system  programs  are	likely	to
       silently change or eliminate the optional ACL entries for these files.

SEE ALSO

       chacl(1), mkdir(1), mkfifo(1), setacl(1), umask(1), lsdev(1M), sam(1M), mknod(2), acl(5), aclv(5), mknod(5).

       HP-UX System Administrator manuals

STANDARDS CONFORMANCE

       mknod: SVID2, SVID3, XPG2

																	 mknod(1M)