MKNOD(2)                             BSD                              MKNOD(2)



NAME
     mknod - make a special file

SYNOPSIS
     mknod(path, mode, dev)
     char *path;
     int mode, dev;

DESCRIPTION
     mknod creates a new file whose name is path.

     In an AES environment, if the final component of the path argument names
     a symbolic link, mknod fails.

     The mode of the new file (including special file bits) is initialized
     from mode.  The protection part of the mode is modified by the process'
     mode mask (see umask(2)).  The first block pointer of the inode is
     initialized from dev and is used to specify which device the special file
     refers to.

     If mode indicates a block or character special file, dev is a
     configuration-dependent specification of a character or block I/O device.
     If mode does not indicate a block special or character special device,
     dev is ignored.

     mknod can be invoked only by the super-user.

     In an AES environment, if the final component of the path argument names
     a symbolic link, mknod fails.

ERRORS
     mknod will fail and the file mode will be unchanged if any of the
     following are true:

     [ENOTDIR]        A component of the path prefix is not a directory.

     [ENAMETOOLONG]   A component of a pathname exceeded 255 characters, or an
                      entire pathname exceeded 1023 characters.

     [ENOENT]         A component of the path prefix does not exist or path
                      points to an empty string.

     [EACCES]         Search permission is denied for a component of the path
                      prefix.

     [ELOOP]          Too many symbolic links were encountered in translating
                      the pathname.

     [EPERM]          The process' effective user ID is not super-user.

     [EIO]            An I/O error occurred while making the directory entry
                      or allocating the inode.

     [ENOSPC]         The directory in which the entry for the new node is
                      being placed cannot be extended because there is no
                      space left on the file system containing the directory.

     [ENOSPC]         There are no free inodes on the file system on which the
                      node is being created.

     [EROFS]          The named file resides on a read-only file system.

     [EEXIST]         The named file exists.

     [EDQUOT]         The directory in which the entry for the new node is
                      being placed cannot be extended because the user's quota
                      of disk blocks on the file system containing the
                      directory has been exhausted.

SEE ALSO
     chmod(2), stat(2), umask(2)

DIAGNOSTICS
     A successful call returns zero.  A failed call returns -1 and sets errno
     as indicated under "Errors."

NOTES
     The following errors, not returned under Domain/OS BSD, may be returned
     under other implementations:

     [EINVAL]         The pathname contains a character with the high-order
                      bit set.

     [EPERM]          The pathname contains a character with the high-order
                      bit set.  "