Lines Matching refs:of

8 Ext2, XFS, JFS, etc. UBIFS represents a separate class of file-systems
10 file-system of this class is JFFS2.
12 To make it more clear, here is a small comparison of MTD devices and
15 1 MTD devices represent flash devices and they consist of eraseblocks of
16   rather large size, typically about 128KiB. Block devices consist of
24 4 Eraseblocks become worn out after some number of erase cycles -
35 UBIFS works on top of UBI. UBI is a separate software layer which may be
38 level abstraction than a MTD device. The programming model of UBI devices
39 is very similar to MTD devices - they still consist of large eraseblocks,
40 they have read/write/erase operations, but UBI devices are devoid of
43 In a sense, UBIFS is a next generation of JFFS2 file-system, but it is
47 * JFFS2 works on top of MTD devices, UBIFS depends on UBI and works on
48   top of UBI volumes.
57 it possible to fit quite a lot of data to the flash.
59 Similarly to JFFS2, UBIFS is tolerant of unclean reboots and power-cuts.
64 UBIFS scales logarithmically (most of the data structures it uses are
66 on the flash size, like in case of JFFS2. This is because UBIFS
71 The authors of UBIFS believe, that it is possible to develop UBI2 which
82 bulk_read		read more in one go to take advantage of flash
85 no_chk_data_crc (*)	skip checking of CRCs on data nodes in order to
88 			of this option is that corruption of the contents
89 			of a file can go unnoticed.
106 Mount "rootfs" volume of UBI device 0 to /mnt/ubifs ("rootfs" is volume
110 The following is an example of the kernel boot arguments to attach mtd0