Lines Matching full:hierarchy

32 file hierarchy, and the related filesystem actions are defined with `access
111 file hierarchy ``/usr``.  Without another rule, write actions would then be
182 It is recommended setting access rights to file hierarchy leaves as much as
184 read-only hierarchy and ``~/tmp/`` as a read-write hierarchy, compared to
185 ``~/`` as a read-only hierarchy and ``~/tmp/`` as a read-write hierarchy.
224 A bind mount mirrors a source file hierarchy to a destination.  The destination
225 hierarchy is then composed of the exact same files, on which Landlock rules can
232 combined in a merge directory, result of the mount point.  This merge hierarchy
234 on the merge hierarchy only reflects on the upper layer.  From a Landlock
238 restrict the resulted merged hierarchy, and vice versa.  Landlock users should
435 from a parent to its hierarchy.  Because files are identified and restricted by
436 their hierarchy, moving or linking a file from one directory to another implies
437 propagation of the hierarchy constraints, or restriction of these actions