Lines Matching refs:directory

34 Max entries per directory	unlimited		unlimited
51 directory data are highly compacted, and packed on byte boundaries.  Each
53 file type, i.e. regular file, directory, symbolic link, and block/char device
84 	|   directory	|
101 the source directory, and checked for duplicates.  Once all file data has been
102 written the completed inode, directory, fragment, export, uid/gid lookup and
127 (regular file, directory, device, etc.), the inode contents and length
131 directory inode are defined: inodes optimised for frequently occurring
139 in a directory table.  Directories are accessed using the start address of
140 the metablock containing the directory and the offset into the
147 Directories are therefore organised in a two level list, a directory
148 header containing the shared start block value, and a sequence of directory
149 entries, each of which share the shared start block.  A new directory header
150 is written once/if the inode start block changes.  The directory
151 header/directory entry list is repeated as many times as necessary.
153 Directories are sorted, and can contain a directory index to speed up
155 storing the index/filename mapping to the first directory header
161 decompressed to do a lookup irrespective of the length of the directory.
255 (i.e. inode or directory) or fragment access.  Because metadata and fragments