Lines Matching full:directories

25 While directories will report an st_dev from the overlay-filesystem,
91 'lower' filesystem is either hidden or, in the case of directories,
109 Directories  chapter
112 Overlaying mainly involves directories.  If a given name appears in both
117 Where both upper and lower objects are directories, a merged directory
120 At mount time, the two directories given as mount options "lowerdir" and
132 actual lookups find directories, both are stored and a merged
136 Only the lists of names from directories are merged.  Other content
143 By default, all access to the upper, lower and work directories is the
153 always be able to delete files or directories, create nodes, or
154 search some restricted directories.  The ability to search and read
163 whiteouts and opaque directories
169 directories (non-directories are always opaque).
184 lower directories are each read and the name lists merged in the
197 seek offsets are assigned sequentially when the directories are read.
209 Readdir on directories that are not merged is simply handled by the
212 renaming directories
269 indication that multiple upper directories may be redirected to the same
278 Non-directories
281 Objects that are not directories (files, symlinks, device-special
362 The specified lower directories will be stacked beginning from the
384 Do not use metacopy=on with untrusted upper/lower directories. Otherwise
572 directories that cannot be decoded from a lower file handle, these
573 directories are copied up on encode and encoded as an upper file handle.
612 indicator that user should throw away upper and work directories and create