Differences between revisions 1 and 54 (spanning 53 versions)
Revision 1 as of 2005-12-23 00:34:43
Size: 194
Comment:
Revision 54 as of 2012-09-10 22:14:04
Size: 1592
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 way more flexible than the current in-kernel unionfs solution.

I'm open to patches, suggestions, whatever... The preferred way is the mailing list at {{{unionfs-fuse (at) googlegroups (dot) com}}} or see [[http://groups.google.com/group/unionfs-fuse|unionfs-fuse on Google Groups]].

If you want to contact me and me only see the [[Contact]] page on how to reach me...

If you've sent me something and think it takes me too long to answer, go check [[UndeliverableMail]] page. I might have problems sending mail to you...

<<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)
 * Advanced features like copy-on-write and more

== Why NOT choose it ==

 * Compared to kernel-space solution we need lots of useless context switches which makes kernel-only solution clear speed-winner (well, actually I've made some tests and the hard-drives seem to be the bottleneck so the speed is fine, too)

<<GoogleAd>>

== Donation ==

If you use the software and like it, please consider a [[Donation|donation]]...

== Download ==

 * Latest version: 0.26 (released 2012-09-11)
 * Archive location: http://podgorny.cz/unionfs-fuse/releases/
 * Repository location: http://hg.podgorny.cz/unionfs-fuse (Mercurial)

unionfs-fuse

This is my effort to create a unionfs filesystem implementation which is way more flexible than the current in-kernel unionfs solution.

I'm open to patches, suggestions, whatever... The preferred way is the mailing list at unionfs-fuse (at) googlegroups (dot) com or see unionfs-fuse on Google Groups.

If you want to contact me and me only see the Contact page on how to reach me...

If you've sent me something and think it takes me too long to answer, go check UndeliverableMail page. I might have problems sending mail to you...

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)
  • Advanced features like copy-on-write and more

Why NOT choose it

  • Compared to kernel-space solution we need lots of useless context switches which makes kernel-only solution clear speed-winner (well, actually I've made some tests and the hard-drives seem to be the bottleneck so the speed is fine, too)

Donation

If you use the software and like it, please consider a donation...

Download