Differences between revisions 3 and 32 (spanning 29 versions)
Revision 3 as of 2006-01-07 17:37:14
Size: 249
Comment:
Revision 32 as of 2007-02-09 16:26:38
Size: 1390
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 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 5: Line 5:
This is still INCOMPLETE!!! I'm open to patches, suggestions, whatever (at radek@podgorny.cz)...
Line 7: Line 7:
attachment:unionfs.c [[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 Pay''''''Pal)...

[[PayPalDonation()]]

== Download ==

 * Latest version: 0.17 (released 2007-02-09)
 * Archive location: http://podgorny.cz/unionfs-fuse/releases/

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

 * 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: