Differences between revisions 3 and 8 (spanning 5 versions)
⇤ ← Revision 3 as of 2006-01-07 17:37:14 →
Size: 249
Editor: RadekPodgorny
Comment:
← Revision 8 as of 2006-01-27 19:00:46 → ⇥
Size: 1111
Editor: RadekPodgorny
Comment:
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
This is my effort to create a unionfs implementation which is probably slower but way more flexible than the current in-kernel unionfs solution. More info will come soon... This is my effort to create a unionfs implementation which is probably slower but way more flexible than the current in-kernel unionfs solution. Currently it's almost fully usable, the only problem is new file/directory creation which I will fix soon...
Line 5: Line 5:
This is still INCOMPLETE!!! == Why choose this stuff ==
Line 7: Line 7:
attachment:unionfs.c  * The filesystem has to be mounted after the roots are mounted when using the standard module. With unionfs-fuse, you can mount the roots later and their contents will appear seamlesly
 * You get caching which speeds things up a lot for free
 * You get nice stats (optional)

== Why NOT choose it ==

 * Compared to kernel-space solution we need lots of useless context switches which makes kernel-only solution clear speed-winner

== Available parameters ==

 * {{{--roots=/root1,/root2}}}
 * {{{--stats}}}

== TODO ==

 * Add support for creating directories
 * Add support for choice which roots are read-only and which are not
 * Add cache controls

== Releases ==

 * Latest version: 0.9 (released 2006-01-27)
 * Archive location: http://podgorny.cz/unionfs-fuse/releases/

unionfs-fuse

This is my effort to create a unionfs implementation which is probably slower but way more flexible than the current in-kernel unionfs solution. Currently it's almost fully usable, the only problem is new file/directory creation which I will fix soon...

Why choose this stuff

  • The filesystem has to be mounted after the roots are mounted when using the standard module. With unionfs-fuse, you can mount the roots later and their contents will appear seamlesly
  • You get caching which speeds things up a lot for free
  • You get nice stats (optional)

Why NOT choose it

  • Compared to kernel-space solution we need lots of useless context switches which makes kernel-only solution clear speed-winner

Available parameters

  • --roots=/root1,/root2

  • --stats

TODO

  • Add support for creating directories
  • Add support for choice which roots are read-only and which are not
  • Add cache controls

Releases