Lines Matching refs:directory

24 all non-directory objects will report an st_dev from the lower or
27 over the lifetime of a non-directory object.  Many applications and
39 It would be more correct to refer to an upper and lower 'directory
41 directory trees to be in the same filesystem and there is no
58 upper and lower filesystems and refers to a non-directory in either,
62 Where both upper and lower objects are directories, a merged directory
66 "upperdir" are combined into a merged directory:
71 The "workdir" needs to be an empty directory on the same filesystem
74 Then whenever a lookup is requested in such a merged directory, the
75 lookup is performed in each actual directory and the combined result
78 directory is created, otherwise only one is stored: the upper if it
83 directory only.  These attributes of the lower directory are hidden.
94 When a whiteout is found in the upper level of a merged directory, any
98 A directory is made opaque by setting the xattr "trusted.overlay.opaque"
99 to "y".  Where the upper filesystem contains an opaque directory, any
100 directory in the lower filesystem with the same name is ignored.
105 When a 'readdir' request is made on a merged directory, the upper and
110 directory is opened and read by two processes at the same time, they
112 directory (offset 0) followed by a readdir will cause the cache to be
115 This means that changes to the merged directory do not appear while a
116 directory is being read.  This is unlikely to be noticed by many
121   - read part of a directory
122   - remember an offset, and close the directory
123   - re-open the directory some time later
128 directory.
131 underlying directory (upper or lower).
149 The copy_up process first makes sure that the containing directory
167 separator character between the directory names.  For example:
197 Symlinks in /proc/PID/ and /proc/PID/fd which point to a non-directory