Home
Main website
Display Sidebar
Hide Ads
Recent Changes
View Source:
mknod(2)
Edit
PageHistory
Diff
Info
LikePages
You are viewing an old revision of this page.
View the current version
.
MKNOD !!!MKNOD NAME SYNOPSIS DESCRIPTION RETURN VALUE ERRORS CONFORMING TO NOTES SEE ALSO ---- !!NAME mknod - create a special or ordinary file !!SYNOPSIS __#include __''pathname''__, mode_t__ ''mode''__, dev_t__ ''dev''__); __ !!DESCRIPTION __mknod__ attempts to create a filesystem node (file, device special file or named pipe) named ''pathname'', specified by ''mode'' and ''dev''. ''mode'' specifies both the permissions to use and the type of node to be created. It should be a combination (using bitwise OR) of one of the file types listed below and the permissions for the new node. The permissions are modified by the process's __umask__ in the usual way: the permissions of the created node are __(mode __. The file type should be one of __S_IFREG__, __S_IFCHR__, __S_IFBLK__ and __S_IFIFO__ to specify a normal file (which will be created empty), character special file, block special file or FIFO (named pipe), respectively, or zero, which will create a normal file. If the file type is __S_IFCHR__ or __S_IFBLK__ then ''dev'' specifies the major and minor numbers of the newly created device special file; otherwise it is ignored. If ''pathname'' already exists, or is a symlink, this call fails with an EEXIST error. The newly created node will be owned by the effective uid of the process. If the directory containing the node has the set group id bit set, or if the filesystem is mounted with BSD group semantics, the new node will inherit the group ownership from its parent directory; otherwise it will be owned by the effective gid of the process. !!RETURN VALUE __mknod__ returns zero on success, or -1 if an error occurred (in which case, ''errno'' is set appropriately). !!ERRORS __EPERM__ ''mode'' requested creation of something other than a FIFO (named pipe), and the caller is not the superuser; also returned if the filesystem containing ''pathname'' does not support the type of node requested. __EINVAL__ ''mode'' requested creation of something other than a normal file, device special file or FIFO. __EEXIST__ ''pathname'' already exists. __EFAULT__ ''pathname'' points outside your accessible address space. __EACCES__ The parent directory does not allow write permission to the process, or one of the directories in ''pathname'' did not allow search (execute) permission. __ENAMETOOLONG__ ''pathname'' was too long. __ENOENT__ A directory component in ''pathname'' does not exist or is a dangling symbolic link. __ENOTDIR__ A component used as a directory in ''pathname'' is not, in fact, a directory. __ENOMEM__ Insufficient kernel memory was available. __EROFS__ ''pathname'' refers to a file on a read-only filesystem. __ELOOP__ Too many symbolic links were encountered in resolving ''pathname''. __ENOSPC__ The device containing ''pathname'' has no room for the new node. !!CONFORMING TO SVr4 (but the call requires privilege and is thus not in POSIX), 4.4BSD. The Linux version differs from the SVr4 version in that it does not require root permission to create pipes, also in that no EMULTIHOP, ENOLINK, or EINTR error is documented. !!NOTES The Austin draft says: mknod__() is to create a FIFO-special file. If ''mode'' is not S_IFIFO or ''dev'' is not 0, the behavior of __mknod__() is unspecified.__ Under Linux, this call cannot be used to create directories or socket files, and cannot be used to create normal files by users other than the superuser. One should make directories with __mkdir__, and FIFOs with __mkfifo__. There are many infelicities in the protocol underlying NFS. Some of these affect __mknod__. !!SEE ALSO close(2), fcntl(2), mkdir(2), mount(2), open(2), read(2), socket(2), stat(2), umask(2), unlink(2), write(2), fopen(3), mkfifo(3) ----
10 pages link to
mknod(2)
:
Man2m
remove(3)
stat(2)
syscalls(2)
unlink(2)
creat(2)
fstat(2)
lstat(2)
open(2)
mkdir(2)
This page is a man page (or other imported legacy content). We are unable to automatically determine the license status of this page.