Lines Matching refs:directory

29 Max entries per directory:	unlimited		unlimited
45 directory data are highly compacted, and packed on byte boundaries.  Each
47 file type, i.e. regular file, directory, symbolic link, and block/char device
78 	|   directory	|
95 the source directory, and checked for duplicates.  Once all file data has been
96 written the completed inode, directory, fragment, export, uid/gid lookup and
121 (regular file, directory, device, etc.), the inode contents and length
125 directory inode are defined: inodes optimised for frequently occurring
133 in a directory table.  Directories are accessed using the start address of
134 the metablock containing the directory and the offset into the
141 Directories are therefore organised in a two level list, a directory
142 header containing the shared start block value, and a sequence of directory
143 entries, each of which share the shared start block.  A new directory header
144 is written once/if the inode start block changes.  The directory
145 header/directory entry list is repeated as many times as necessary.
147 Directories are sorted, and can contain a directory index to speed up
149 storing the index/filename mapping to the first directory header
155 decompressed to do a lookup irrespective of the length of the directory.
249 (i.e. inode or directory) or fragment access.  Because metadata and fragments