Lines Matching full:file

4 ROMFS - ROM File System
11 file system which doesn't take up useful memory from the router
23 To create such a file system, you'll need a user program named
51 byte boundaries for fast access.  The minimum space a file will take
52 is 32 bytes (this is an empty file, with a less than 16 character
53 name).  The maximum overhead for any non-empty file is the header, and
55 bytes.  This is quite rare however, since most file names are longer
74  xx	|     file	|
90 The following bytes are now part of the file system; each file header
96   0	| next filehdr|X|	The offset of the next file header
100   8	|     size      |	The size of this file in bytes
102  12	|   checksum	|	Covering the meta data, including the file
104  16	| file name     |	The zero terminated name of the file,
107  xx	| file data	|
110 Since the file headers begin always at a 16 byte boundary, the lowest
113 the file; while bit 4 shows if the file is executable or not.  The
117 file is user and group 0, this should never be a problem for the
118 intended use.  The mapping of the 8 possible values to file types is
124  0	hard link	link destination [file header]
125  1	directory	first file's header
126  2	regular file	unused, must be zero [MBZ]
127  3	symbolic link	unused, MBZ (file data is the link content)
143 directly after the (padded) file name.
145 Another thing to note is that romfs works on file headers and data
148 To overcome this limitation, the whole size of the file system must be
151 If you have any problems or suggestions concerning this file system,
154 this file system is the small code.  On the other hand, don't be
171 - The file system is read only, so it can be very small, but in case
172   one would want to write _anything_ to a file system, he still needs
173   a writable file system, thus negating the size advantages.  Possible
179   from the filesystem.  It might be resolved by reordering file data to
182   the file contents to the mm subsystem.