Lines Matching refs:filesystems

28 by different filesystems. It handles common things like making the filesystem
49 listed in /proc/filesystems, but calling mount can also trigger a module load
56 Different drivers implement different filesystems, which have four categories:
58 1) Block device backed filesystems, such as ext2 and vfat.
61 through. The source argument for block backed filesystems is a path to a
66 Block backed filesystems are the "conventional" filesystem type most people
70 2) Server backed filesystems, such as cifs/samba or fuse.
81 …urce argument for these filesystems indicates where the filesystem lives. It's often in a URL-like…
83 A lot of server backed filesystems want to open their own connection so they
93 These are also known as "pipe backed" filesystems (or "network filesystems"
95 Conceptually they're char device backed filesystems (analogus to the block
100 3) Ram backed filesystems, such as ramfs and tmpfs.
102 These are very simple filesystems that don't implement a backing store. Data
125 backed filesystems: one driver provides /dev/ram0 and the second driver mounts
133 4) Synthetic filesystems, such as proc, sysfs, devpts...
135 These filesystems don't have any backing store either, because they don't
136 store arbitrary data the way the first three types of filesystems do.
152 Those are the four types of filesystems: backing store can be a fixed length
157 And that's how filesystems get mounted, using the mount system call which has
159 one of those filesystems, and the "source" and "data" arguments get fed to