Lines Matching +full:system +full:- +full:on +full:- +full:module
1 ROMFS - ROM FILE SYSTEM
7 file system which doesn't take up useful memory from the router
11 defunct) filesystems, compiled as module need more than 20000 bytes,
15 nfs module with nfsroot is about 57K. Furthermore, as a bit unfair
19 To create such a file system, you'll need a user program named
20 genromfs. It is available on http://romfs.sourceforge.net/
22 As the name suggests, romfs could be also used (space-efficiently) on
23 various read-only media, like (E)EPROM disks if someone will have the
27 which has only this filesystem linked in, and then can load any module
28 later, with the current module utilities. It can also be used to run
30 floppy drives can be loaded later if you use the "initrd"--initial
31 RAM disk--feature of the kernel. This would not be really news
37 module. The kernel can be small enough, since it doesn't have other
38 filesystems, like the quite large ext2fs module, which can then be
45 romfs operates on block devices as you can expect, and the underlying
46 structure is very simple. Every accessible structure begins on 16
49 name). The maximum overhead for any non-empty file is the header, and
58 +---+---+---+---+
59 0 | - | r | o | m | \
60 +---+---+---+---+ The ASCII representation of those bytes
61 4 | 1 | f | s | - | / (i.e. "-rom1fs-")
62 +---+---+---+---+
64 +---+---+---+---+
66 +---+---+---+---+
69 +---+---+---+---+
74 now on) must be in big endian order.
86 The following bytes are now part of the file system; each file header
87 must begin on a 16 byte boundary.
91 +---+---+---+---+
93 +---+---+---+---+ (zero if no more files)
95 +---+---+---+---+
97 +---+---+---+---+
99 +---+---+---+---+ name, and padding
102 +---+---+---+---+
123 5 char device - " -
132 using the executable bits for special purposes on the socket and fifo
138 Another thing to note is that romfs works on file headers and data
140 device drivers are unable to cope with smaller than block-sized data.
141 To overcome this limitation, the whole size of the file system must be
144 If you have any problems or suggestions concerning this file system,
147 this file system is the small code. On the other hand, don't be
156 to romfs-subscribe@shadow.banki.hu, the content is irrelevant.
160 - Permissions and owner information are pretty essential features of a
161 Un*x like system, but romfs does not provide the full possibilities.
164 - The file system is read only, so it can be very small, but in case
165 one would want to write _anything_ to a file system, he still needs
166 a writable file system, thus negating the size advantages. Possible
167 solutions: implement write access as a compile-time option, or a new,
170 - Since the files are only required to have alignment on a 16 byte
177 - Compression might be an useful feature, but memory is quite a
180 - Where it is used?
182 - Does it work on other architectures than intel and motorola?