Penguin
Recent Changes
Annotated edit history of mknod(2) version 2, including all changes. View license author blame.
Rev Author # Line
1 perry 1 !!NAME
2 mknod - create a special or ordinary file
3 !!SYNOPSIS
2 PerryLorier 4 #include <sys/types.h>
5 #include <sys/stat.h>
6 #include <fcntl.h>
7 #include <unistd.h>
1 perry 8
2 PerryLorier 9 __int mknod(const char *__''pathname''__, mode_t __''mode''__, dev_t__'' dev''__);__
1 perry 10
11 !!DESCRIPTION
2 PerryLorier 12 mknod(2) attempts to create a filesystem node (file, device special file or named pipe) named ''pathname'', specified by ''mode'' and ''dev''.
1 perry 13
2 PerryLorier 14 ''mode'' specifies both the permissions to use and the type of node to be created.
1 perry 15
2 PerryLorier 16 It should be a combination (using bitwise OR) of one of the file types listed below and the permissions for the new node.
1 perry 17
2 PerryLorier 18 The permissions are modified by the process's __umask__ in the usual way: the permissions of the created node are __(mode & ~umask)__.
1 perry 19
2 PerryLorier 20 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.
1 perry 21
2 PerryLorier 22 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
1 perry 23 ignored.
24
2 PerryLorier 25 If ''pathname'' already exists, or is a symlink, this call fails with an [EEXIST] error.
1 perry 26
2 PerryLorier 27 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.
1 perry 28
29 !!RETURN VALUE
2 PerryLorier 30 mknod(2) returns zero on success, or -1 if an error occurred (in which case, ''errno'' is set appropriately).
1 perry 31
32 !!ERRORS
2 PerryLorier 33 ;[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.
34 ;[EINVAL]: ''mode'' requested creation of something other than a normal file, device special file or FIFO.
35 ;[EEXIST]: ''pathname'' already exists.
36 ;[EFAULT]: ''pathname'' points outside your accessible address space.
37 ;[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.
38 ;[ENAMETOOLONG]: ''pathname'' was too long.
39 ;[ENOENT]: A directory component in ''pathname'' does not exist or is a dangling symbolic link.
40 ;[ENOTDIR]: A component used as a directory in ''pathname'' is not, in fact, a directory.
41 ;[ENOMEM]: Insufficient kernel memory was available.
42 ;[EROFS]: ''pathname'' refers to a file on a read-only filesystem.
43 ;[ELOOP]: Too many symbolic links were encountered in resolving ''pathname''.
44 ;[ENOSPC]: The device containing ''pathname'' has no room for the new node.
1 perry 45
46 !!CONFORMING TO
2 PerryLorier 47 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
48 create pipes, also in that no [EMULTIHOP], [ENOLINK], or [EINTR] error is documented.
1 perry 49
50 !!NOTES
2 PerryLorier 51 POSIX 1003.1&#8208;2001 says: "The only portable use of mknod() is to create a FIFO&#8208;special file. If mode is not S_IFIFO or dev is not 0, the behavior of mknod() is unspecified."
1 perry 52
2 PerryLorier 53 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(2), and FIFOs with mkfifo(2).
1 perry 54
2 PerryLorier 55 There are many infelicities in the protocol underlying NFS. Some of these affect mknod(2).
1 perry 56
57 !!SEE ALSO
2 PerryLorier 58 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)
This page is a man page (or other imported legacy content). We are unable to automatically determine the license status of this page.

PHP Warning

lib/blame.php:177: Warning: Invalid argument supplied for foreach() (...repeated 8 times)