Lines Matching refs:be

15 many use cases will be able to ignore these differences.
19 cases an object accessed in the union will be indistinguishable
26 only be unique when combined with st_dev, and both of these can change
28 tools ignore these values and will not be affected.
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
42 requirement that the root of a filesystem be given for either upper or
45 The lower filesystem can be any filesystem supported by Linux and does
46 not need to be writable.  The lower filesystem can even be another
47 overlayfs.  The upper filesystem will normally be writable and if it
71 The "workdir" needs to be an empty directory on the same filesystem
112 directory (offset 0) followed by a readdir will cause the cache to be
116 directory is being read.  This is unlikely to be noticed by many
126 there may be little correlation between the old and new locations in
146 The copy_up may turn out to be unnecessary, for example if the file is
160 rename or unlink will of course be noticed and handled).
166 Multiple lower layers can now be given using the the colon (":") as a
171 As the example shows, "upperdir=" and "workdir=" may be omitted.  In
172 that case the overlay will be read-only.
174 The specified lower directories will be stacked beginning from the
175 rightmost one and going left.  In the above example lower1 will be the
183 moves it over to the old name.  The new file may be on a different
194 "break" the link.  Changes will not be propagated to other names
199 relative paths leading up to the filesystem's root.  This will be
204 be addressed in the future.