Lines Matching +full:512 +full:- +full:bytes

1 .. SPDX-License-Identifier: GPL-2.0
4 ROMFS - ROM File System
15 defunct) filesystems, compiled as module need more than 20000 bytes,
16 while romfs is less than a page, about 4000 bytes (assuming i586
26 As the name suggests, romfs could be also used (space-efficiently) on
27 various read-only media, like (E)EPROM disks if someone will have the
34 floppy drives can be loaded later if you use the "initrd"--initial
35 RAM disk--feature of the kernel.  This would not be really news
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
56 than 3 bytes, and shorter than 15 bytes.
62 	+---+---+---+---+
63   0	| - | r | o | m |  \
64 	+---+---+---+---+	The ASCII representation of those bytes
65   4	| 1 | f | s | - |  /	(i.e. "-rom1fs-")
66 	+---+---+---+---+
67   8	|   full size	|	The number of accessible bytes in this fs.
68 	+---+---+---+---+
69  12	|    checksum	|	The checksum of the FIRST 512 BYTES.
70 	+---+---+---+---+
73 	+---+---+---+---+
80 The first eight bytes identify the filesystem, even for the casual
82 bytes accessible from the start of this filesystem.  The 4th longword
83 is the checksum of the first 512 bytes (or the number of bytes
90 The following bytes are now part of the file system; each file header
95      	+---+---+---+---+
97 	+---+---+---+---+	  (zero if no more files)
99 	+---+---+---+---+
100   8	|     size      |	The size of this file in bytes
101 	+---+---+---+---+
103 	+---+---+---+---+	  name, and padding
106 	+---+---+---+---+
129  5	char device		    - " -
142 have a nonzero size field; they contain the number of bytes available
147 device drivers are unable to cope with smaller than block-sized data.
163 to romfs-subscribe@shadow.banki.hu, the content is irrelevant.
167 - Permissions and owner information are pretty essential features of a
171 - The file system is read only, so it can be very small, but in case
174   solutions: implement write access as a compile-time option, or a new,
177 - Since the files are only required to have alignment on a 16 byte
184 - Compression might be an useful feature, but memory is quite a
187 - Where it is used?
189 - Does it work on other architectures than intel and motorola?