Write access to the directory containing pathname is
not allowed for the process's effective UID, or one of the directories in
pathname did not allow search permission. (See also
EBUSY (not on Linux)
The file pathname cannot be unlinked because it is
being used by the system or another process and the implementation
considers this an error.
pathname points outside your accessible address
An I/O error occurred.
pathname refers to a directory. (This is the
non-POSIX value returned by Linux since 2.1.132.)
Too many symbolic links were encountered in translating
pathname was too long.
A component in pathname does not exist or is a
dangling symbolic link, or pathname is empty.
Insufficient kernel memory was available.
A component used as a directory in pathname is not,
in fact, a directory.
The system does not allow unlinking of directories, or
unlinking of directories requires privileges that the current process
doesn't have. (This is the POSIX prescribed error return.)
EPERM (Linux only)
The filesystem does not allow unlinking of files.
EPERM or EACCES
The directory containing pathname has the sticky bit
(S_ISVTX) set and the process's effective UID is neither the UID of
the file to be deleted nor that of the directory containing it, and the
process is not privileged (Linux: does not have the CAP_FOWNER
pathname refers to a file on a read-only