The common members definition behind Rights and Abilities. Some operations may apply
only to certain node types (e.g. [Operations.MODIFY_DIRECTORY] only applies to directories).
Options which can be used when opening nodes. Unlike Flags, these options are designed for
specific use cases (e.g. to reduce round-trip latency when requesting attributes).
Specifies that this object is not linkable. This is only intended to be used in the context of
creating a temporary unnamed objects. When that is not the case, the node protocol defines if it
is linkable (i.e. if it composes the Linkable protocol). When this flag is set along with
Flags.FLAG_CREATE_AS_UNNAMED_TEMPORARY, an unnamed temporary object will be created that
cannot be linked into the filesystem. This would be similar to Linux O_TMPFILE | O_EXCL.
Set of rights that [Flags.PERM_INHERIT_WRITE] will inherit from the parent connection if
specified. Note that if any of these permissions are missing from the connection, none of these
permissions will be inherited.
Bits reserved for posix protections. Native fuchsia filesystems
are not required to set bits contained within MODE_PROTECTION_MASK,
but filesystems that wish to do so may refer to sys/stat.h for their
definitions.
Bits indicating node type. The canonical mechanism to check
for a node type is to take ‘mode’, bitwise AND it with the
MODE_TYPE_MASK, and check exact equality against a mode type.
The name of an extended attribute. It can not contain any null bytes. Other
than that and the maximum size, no particular structure is imposed on the
name.
Rights are properties specific to a connection. They limit which operations are allowed on a
connection, including those which may be granted to new connections.