Lines Matching full:hierarchy

38     For these rules, the object is a file hierarchy,
132 file hierarchy ``/usr``.  Without another rule, write actions would then be
216 It is recommended setting access rights to file hierarchy leaves as much as
218 read-only hierarchy and ``~/tmp/`` as a read-write hierarchy, compared to
219 ``~/`` as a read-only hierarchy and ``~/tmp/`` as a read-write hierarchy.
258 A bind mount mirrors a source file hierarchy to a destination.  The destination
259 hierarchy is then composed of the exact same files, on which Landlock rules can
266 combined in a merge directory, result of the mount point.  This merge hierarchy
268 on the merge hierarchy only reflects on the upper layer.  From a Landlock
272 restrict the resulted merged hierarchy, and vice versa.  Landlock users should
470 from a parent to its hierarchy.  Because files are identified and restricted by
471 their hierarchy, moving or linking a file from one directory to another implies
472 propagation of the hierarchy constraints, or restriction of these actions