> I realize that mangling to 255 bytes is indeed a required measure to > take when returning file names to fuse_fill_dir_t. But going further, > mangling combined with a ATTR_CMN_NAME implementation, the very same way > that the HFS+ driver does it, should at least satisfy Finder (maybe even > Carbon/Cocoa's file managers) and make it use the full version of these > very long filenames, or is that conclusion incorrect?
To provide a "full" name through ATTR_CMN_NAME, MacFUSE will have to talk to the user-space file system, which means the kernel-user API (the FUSE API in ntfs-3g's case) will have to be extended, which means the user-space file system will, in addition to mangling, also have to implement the new callback(s). Amit --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
