Differences between revisions 22 and 32 (spanning 10 versions)
⇤ ← Revision 22 as of 2006-07-02 18:23:07 →
Size: 1614
Editor: RadekPodgorny
Comment:
← Revision 32 as of 2007-02-09 16:26:38 → ⇥
Size: 1390
Editor: RadekPodgorny
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
= Foreword = = unionfs-fuse =
Line 3: Line 3:
This is my effort to create a unionfs filesystem 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... This is my effort to create a unionfs filesystem implementation which is probably slower but way more flexible than the current in-kernel unionfs solution. Currently it's almost fully usable, will only minor convenience issues to be fixed...
Line 19: Line 19:
== Available parameters ==

 * {{{--roots=/root1,/root2}}}
 * {{{--stats}}}
Line 26: Line 21:
 * Add support for creating directories
Line 33: Line 27:
== Donation ==

If you use the software and like it, please consider a donation (provided by Pay''''''Pal)...

[[PayPalDonation()]]
Line 35: Line 35:
 * Latest version: 0.14 (released 2006-07-02)  * Latest version: 0.17 (released 2007-02-09)
Line 38: Line 38:
If you want to follow the development closely, see my experimental mercurial repository at: If you want to follow the development closely, see my mercurial repository at:
Line 40: Line 40:
 * http://podgorny.cz/~radek/hg/hgwebdir.cgi/home/radek/hg/unionfs-fuse

My older tinyrcs repository is at:

 * http://podgorny.cz/~radek/rep/unionfs-fuse/

(tinyrcs is my currently-under-development revision control system) -> ["TinyRCS"]		  * http://hg.podgorny.cz/unionfs-fuse

unionfs-fuse

This is my effort to create a unionfs filesystem implementation which is probably slower but way more flexible than the current in-kernel unionfs solution. Currently it's almost fully usable, will only minor convenience issues to be fixed...

I'm open to patches, suggestions, whatever (at radek@podgorny.cz)...

GoogleAd()

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

TODO

  • Add support for choice which roots are read-only and which are not
  • Add cache controls
  • Handle writing to /stats intelligently

GoogleAd()

Donation

If you use the software and like it, please consider a donation (provided by PayPal)...

PayPalDonation()

Download

If you want to follow the development closely, see my mercurial repository at: