...t can be passed as the dirfd argument in system calls such as fstatat (2), fchownat (2), fchmodat (2), linkat (2), and readlinkat (2), in order to operate on the symbolic link i…...d to users with appropriate capabilities for directories with the sticky bit set (see the chmod (1) manual page for an explanation of the sticky bit). Filesystem differences The…...rm (2) bind (2) cfgetispeed (3) cfgetospeed (3) cfsetispeed (3) cfsetospeed (3) chdir (2) chmod (2) chown (2) clock_gettime (2) close (2) connect (2) creat (2) dup (2) dup2 (2) …...ase. Permissions The permission bits of a file consist of three groups of three bits; see chmod (1) and stat (2). The first group of three is used when the effective user ID of …...ed actions accessible through these system call families: chdir (2), stat (2), flock (2), chmod (2), chown (2), setxattr (2), utime (2), ioctl (2), fcntl (2), access (2). Future…...reliable information are st_mode , st_nlink , st_uid , and st_gid . All files support the chmod (2)/ fchmod (2) and chown (2)/ fchown (2) operations, but will not be able to gra…...1-2001 and/or POSIX.1-2008: access() asctime() asctime_r() catclose() catgets() catopen() chmod() [Added in POSIX.1-2008] chown() [Added in POSIX.1-2008] closedir() closelog() c…...he owner, group, and permissions of a pathname socket can be changed (using chown (2) and chmod (2)). Abstract sockets Socket permissions have no meaning for abstract sockets: t…...g., read (2), execve (2)). IN_ATTRIB (*) Metadata changed—for example, permissions (e.g., chmod (2)), timestamps (e.g., utimensat (2)), extended attributes ( setxattr (2)), link…...at normally require the filesystem UID of the process to match the UID of the file (e.g., chmod (2), utime (2)), excluding those operations covered by CAP_DAC_OVERRIDE and CAP_D…