-EXDEV |
Existing file and new link pathnames are not on the same filesystem. |
-EPERM |
The filesystem containing existing file and new link does not support the creation of hard links. |
-EFAULT |
ebx or ecx points outside your accessible address space. |
-EACCES |
Write access to the directory containing new link is not allowed for the process's effective UID, or one of the directories in Existing file path or new link path did not allow search (execute) permission. |
-ENAMETOOLONG |
Existing file or new link pathname was too long. |
-ENOENT |
A directory component in existing file or new link pathname does not exist or is a dangling symbolic link. |
-ENOTDIR |
A component used as a directory in existing file or new link pathname is not, in fact, a directory. |
-ENOMEM |
Insufficient kernel memory was available. |
-EROFS |
The file is on a read-only filesystem. |
-EEXIST |
Path pointed by ecx already exists. |
-EMLINK |
The file referred to by ebx already has the maximum number of links to it. |
-ELOOP |
Too many symbolic links were encountered in resolving existing file or new link pathname. |
-ENOSPC |
The device containing the file has no room for the new directory entry. |
-EPERM |
Path pointed by ebx is a directory. |
-EIO |
An I/O error occurred. |