Difference between revisions of "File systems"
From Organic Design wiki
m (Caretaker: headings) |
(update) |
||
| Line 1: | Line 1: | ||
| − | [[Category: | + | [[Category:peerix]] |
| − | + | The [[:Kernel]] requires a filesystem to start up. In unix terms this means it's ''/sbin/init'' or ''/linuxrc''. It's also important that the OS is able to read and write all common file systems. | |
| − | + | = FUSE = | |
| − | |||
| − | = | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
User-space implementation of a filesystem API. | User-space implementation of a filesystem API. | ||
| − | *Requires kernel module | + | *Requires kernel module that is standard in 2.6 kernels |
*Good examples of custom implementation | *Good examples of custom implementation | ||
**See [[fs.c]] | **See [[fs.c]] | ||
| + | |||
| + | = NTFS = | ||
| + | libntfs uses FUSE to impelment a file system wrapper for NTFS | ||
Revision as of 02:42, 22 December 2006
The Kernel requires a filesystem to start up. In unix terms this means it's /sbin/init or /linuxrc. It's also important that the OS is able to read and write all common file systems.
FUSE
User-space implementation of a filesystem API.
- Requires kernel module that is standard in 2.6 kernels
- Good examples of custom implementation
- See fs.c
NTFS
libntfs uses FUSE to impelment a file system wrapper for NTFS
