...y). EPERM The filesystem containing pathname does not support the removal of directories. EROFS pathname refers to a directory on a read-only filesystem. STANDARDS POSIX.1-2008.…...ivilege to enable process accounting. On Linux, the CAP_SYS_PACCT capability is required. EROFS filename refers to a file on a read-only filesystem. EUSERS There are no more fre…...file, and the caller is not privileged (Linux: does not have the CAP_FOWNER capability). EROFS path resides on a read-only filesystem. STANDARDS POSIX.1-2008. HISTORY utime () S…...file, and the caller is not privileged (Linux: does not have the CAP_FOWNER capability). EROFS path resides on a read-only filesystem. STANDARDS POSIX.1-2008. HISTORY utime () S…...he file when the error was recorded. ENOSPC Disk space was exhausted while synchronizing. EROFS EINVAL fd is bound to a special file (e.g., a pipe, FIFO, or socket) which does n…...he file when the error was recorded. ENOSPC Disk space was exhausted while synchronizing. EROFS EINVAL fd is bound to a special file (e.g., a pipe, FIFO, or socket) which does n…...beyond its current size. EPERM The operation was prevented by a file seal; see fcntl (2). EROFS The named file resides on a read-only filesystem. ETXTBSY The file is an executab…...beyond its current size. EPERM The operation was prevented by a file seal; see fcntl (2). EROFS The named file resides on a read-only filesystem. ETXTBSY The file is an executab…...EPERM The filesystem containing linkpath does not support the creation of symbolic links. EROFS linkpath is on a read-only filesystem. STANDARDS POSIX.1-2008. HISTORY symlink ()…...EPERM The filesystem containing linkpath does not support the creation of symbolic links. EROFS linkpath is on a read-only filesystem. STANDARDS POSIX.1-2008. HISTORY symlink ()…...y. EPERM The filesystem containing pathname does not support the creation of directories. EROFS pathname refers to a file on a read-only filesystem. VERSIONS Under Linux, apart …...y. EPERM The filesystem containing pathname does not support the creation of directories. EROFS pathname refers to a file on a read-only filesystem. VERSIONS Under Linux, apart …...beyond its current size. EPERM The operation was prevented by a file seal; see fcntl (2). EROFS The named file resides on a read-only filesystem. ETXTBSY The file is an executab…...beyond its current size. EPERM The operation was prevented by a file seal; see fcntl (2). EROFS The named file resides on a read-only filesystem. ETXTBSY The file is an executab…...t kernel memory was available. ENOTDIR A component of the path prefix is not a directory. EROFS The socket inode would reside on a read-only filesystem. STANDARDS POSIX.1-2008. …...e file to be unlinked is marked immutable or append-only. (See FS_IOC_SETFLAGS (2const).) EROFS pathname refers to a file on a read-only filesystem. The same errors that occur f…...e file to be unlinked is marked immutable or append-only. (See FS_IOC_SETFLAGS (2const).) EROFS pathname refers to a file on a read-only filesystem. The same errors that occur f…...turned if the filesystem containing pathname does not support the type of node requested. EROFS pathname refers to a file on a read-only filesystem. VERSIONS POSIX.1-2001 says: …...turned if the filesystem containing pathname does not support the type of node requested. EROFS pathname refers to a file on a read-only filesystem. VERSIONS POSIX.1-2001 says: …...lity). EPERM The file is marked immutable or append-only. (See FS_IOC_SETFLAGS (2const).) EROFS The named file resides on a read-only filesystem. VERSIONS C library/kernel diffe…