Hi Jeff, > >> Does anyone know why the libfuse patches never made it upstream? Did >> Amit simply not try? Or did upstream reject the changes? > > Amit had long taken a stand that "MacFUSE is not FUSE" and the 2.7.3 > release achieves all that he wanted. I think he tried to avoid > promising any type of assured compatibility between FUSE for Linux et. > al. and MacFUSE. A pretty reasonable policy if you ask me. > > What does upstream libfuse help with?
>From what I know there are filesystems that require a newer version than >2.7.3. And of course this step would restore compatibility. If you develop a >filesystem that is used on Linux and Mac OS X or port a filesystem from Linux >this could make the whole process easier. In addition to that, newer versions >of libfuse will most likely contain bug fixes. Just my thoughts. Regards, Benjamin -- You received this message because you are subscribed to the Google Groups "MacFUSE" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/macfuse?hl=en.
