Difference between revisions of "File systems"
From Organic Design wiki
m (Caretaker: categories) |
(add fuse) |
||
| Line 1: | Line 1: | ||
[[Category:Articles that need updating]][[Category:peerix]] | [[Category:Articles that need updating]][[Category:peerix]] | ||
{{stub}} | {{stub}} | ||
| − | It's important that the OS is able to read and write all common file systems. Because it is based on Linux most file systems are natively supported, with the exception of NTFS. | + | |
| + | It's important that the OS is able to read and write all common file systems. | ||
| + | ==NTFS== | ||
| + | Because it is based on Linux most file systems are natively supported, with the exception of NTFS. | ||
There is a utilty called Captive that can provide a read/write NTFS file system layer that will integrate with the OS in the normal way. | There is a utilty called Captive that can provide a read/write NTFS file system layer that will integrate with the OS in the normal way. | ||
*[http://www.jankratochvil.net/project/captive/ Captive home page] | *[http://www.jankratochvil.net/project/captive/ Captive home page] | ||
| + | |||
| + | ==Fuse== | ||
| + | User-space implementation of a filesystem API. | ||
| + | *Requires kernel module | ||
| + | *Good examples of custom implementation | ||
| + | **See [[Peerix filesystem]] | ||
Revision as of 01:44, 12 November 2006
|
It's important that the OS is able to read and write all common file systems.
NTFS
Because it is based on Linux most file systems are natively supported, with the exception of NTFS.
There is a utilty called Captive that can provide a read/write NTFS file system layer that will integrate with the OS in the normal way.
Fuse
User-space implementation of a filesystem API.
- Requires kernel module
- Good examples of custom implementation
